Share
ReportWe are working with Dynamics 365 Field Service and noticed something confusing regarding the Time Entry Type field (msdyn_timeentry.msdyn_type).
The field uses the global choice:
msdyn_timeentrytype
Using standard Dataverse customization, we are able to:
- Edit the global choice
- Add new custom values
- Publish successfully
- See the new values appear correctly in forms and dropdowns
However, when attempting to change the status to "Submitted" or "Approved" a Time Entry record using one of the newly added values, the save fails with a managed Field Service plugin error:
Field Service: Update (pre-operation) for msdyn_timeentry
ApiExceptionMessageName: InvalidArgumentThe exception comes from:
Microsoft.Dynamics.FieldService.FieldServicePlugin
Questions:
- Is
msdyn_timeentrytypeofficially extensible for custom values? - If custom values are not supported, is this documented anywhere?
- Why does Dataverse allow extending the choice and publishing values if the managed Field Service logic rejects them at runtime?
- Is there an additional registration/configuration step required for Field Service to recognize new values?
We are trying to understand whether:
- this is unsupported by design,
- there is a missing configuration step,
- or this is a product/documentation gap.
Any clarification from Microsoft or others who have implemented this successfully would be appreciated.
Categories:
I have the same question (0)
All responses (
Answers (
91
