You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A potential workaround could be to include a minified version of apex-mdapi that can deploy the metadata type BusinessHoursSettings.
24.04.2022: Apex-mdapi have wrong Datatype in class MetadatService.BusinessHoursEntry. All DateTime should be Time. Will maybe file a bug to there repo. Some rubbish test code is added in the script folder. Able to create xml file, but deployment fails with unkown error.
The text was updated successfully, but these errors were encountered:
When trying to use class MetadataService.BusinessHoursEntry it's returning that the DataType DateTime is wrong and should be time.
23:02:15.330 (2515433145)|EXCEPTION_THROWN|[13265]|System.CalloutException: Web service callout failed: WebService returned a SOAP Fault: '2022-04-23T22:00:00.000Z' is not a valid value for the type xsd:time faultcode=soapenv:Client faultactor=
After changing all DateTime to Time i have the following error message returned.
System.UnexpectedException: Got an unexpected error in callout : Unsupported type: Time. Contact support with error ID: 185571183-157238 (840816463)
Changing the DataType to String and passing the Time in as String fixed the deployment issue :)
The example flow will create the holiday records and find the default Business hour config, but will not assosicate the holiday records with business hour config.
Check out the salesforce ide here https://ideas.salesforce.com/s/idea/a0B8W00000GddBHUAZ/expose-junction-between-business-hours-and-holidays
A potential workaround could be to include a minified version of apex-mdapi that can deploy the metadata type BusinessHoursSettings.
24.04.2022: Apex-mdapi have wrong Datatype in class MetadatService.BusinessHoursEntry. All DateTime should be Time. Will maybe file a bug to there repo. Some rubbish test code is added in the script folder. Able to create xml file, but deployment fails with unkown error.
The text was updated successfully, but these errors were encountered: