Check out the latest Field Service updates!Learn about the key capabilities and features of Dynamics 365 Field Service and experience some of the new features.
Download overview guide | Watch Field Service video
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Environment: Dynamics 365 online, version 9.1 2020 release wave 1 enabled
The Time Entry entity is shared between Field Service and Project Service/Project Resource Hub, and we use both parts of D365 in our world. Construction side is run through Projects, and the Service part is working through Field Service. Resources are shared in some cases, so we would like to use a single interface to create all entries.
We also like to use these entries as source for time consolidation on a daily/weekly time sheet.
As such, all time entries should have a start and end time.
I created a new Time Entry form where the tech can select the proper Time Source, enter start and end time, duration, add a description etc.
Based on the Time Source however, the tech should either enter the Work Order or project, so a business rule is hiding/displaying the appropriate fields.
The odd thing happening is when a Time Entry is saved. After clicking the Save button, all fields on the form become visible. I created an onSave script to reinforce the hide/display action already implemented through the Business rule, but it made no difference. I also tried different applications if the ‘Visible by default’ attribute, but it made no difference on the behavior.
Disabling the default onSave function (FieldService.TimeEntry.Library.onSave) from the form did not help either.
Does anyone have an idea where this reset of the field visibility is triggered?
Right now, the time entry calendar and the functionality you're experiencing is, from my understanding known and the PM teams are working on things for the future. When the time source is Field Service, the Project related fields will NOT display. This is expected in today's world. Tomorrow, things could be different, very different based on my discussions.
Thank you Scott,
the default forms for time entry in Field Service do indeed not define the Project fields at all. We were trying to create a single form to use for Field Service and Project Service time entries. That is when we encountered the behavior where all defined fields on the form would become visible when saving the form.
Maybe future changes will get us closer to what we envision this will be. Until then, we might just have to rely less on what is there today and create additional customization.
Business Applications communities