Fix DateTimeExtraction model - Bug Fix

[arolshan]

Description

Checklist

• [v] I have read the Submitting Changes section of CONTRIBUTING.md
• [v] The title of the PR is clear and informative
• [v] The appropriate change log has been updated
• [v] The PR does not introduce breaking changes
• [v] If applicable, the changes made in the PR have proper test coverage
• [v] For public API changes to cmdlets:
  • [v] the changes have gone through a cmdlet design review (Microsoft internal partners only)
  • [v] the cmdlet markdown files were generated using the platyPS module

[markcowl]

Also, please add a changelog entry under src\Monitor\Monitor for this

[arolshan]

Also, please add a changelog entry under src\Monitor\Monitor for this

sure

[markcowl]

@arolshan Please respond - if this is a model that is part of cmdlet output (or input), then removing a property is a breaking change. Also, it is unclear to me how this property would be populated, can you explain?

If something has changed in the underlying API, then you need to mitigate the break, which would mean keeping the current string property, adding a new property with the new value, and ensuring that the properties are populated by the cmdlet. Adding a CmdletBreakingChangeAttribute to the model property.

changing this would be breaking change. Thats how the model is in the backend server