Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
2020 release wave 1 Discover 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 Timeline
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
Any reasonable easy and supported way to display only the Time part of the Time Window Start and Time Window End fields in columns
- all standard views, i.e. Work Order view
- in Schedule Board's Requirement Views
Time Window Start & Time Window End both are DateTIme fields. Displaying time only in view is not possible in a supported way. (to my knowledge)
There is a work around to display time only for your requirement.
Please add another field called "new time window start". Copy time value from "Time Window Start" to the new field. (via script / plugin). Use the new field only for views.
Did you find the solution for this? If yes, please close the thread by marking an answer as verified.
This is incorrect. There are two sets of fields: Date Window Start / End: These show Date only. Then there are Time Window Start / End - they show Time Only. There is no need to create new fields because these already exist. Since you want to display time only, why not show Time Window Start and Time Window End?
Hi Scott LeFante
It appears "Time Window Start" and "Time Window End" are date time fields.
Am i missing something? Please help to understand.
Thanks in advance.
There is a way to show only time part of Time window start and Time window End.
1. go to your entity
2. select the field (Time Window Start/Time Window End) which you are using
3. go to change properties
4. go to controls(last tab in field properties)
5. add control Time without Date
6. save and then publish your form
then you will be able to see the Time only format.
Please see the below screenshot for your reference.
@Scott & Shilpi: "Time Window Start" is a datetime field, only the control displaying it ON THE FORM is a "Time Only" control. This means this is no solution for all the VIEWS, which was what I was asking about.
@ba365guy: you'll have a problem if somebody from a different time zone than the dispatcher is creating the work order. If you have a script/plugin/workflow writing the time in "new time window start", you loose the User Local context of the original field.So you might have a "time window start" of 9am but a "new time window start" of 10am in Schedule Board than.
=> not really best solution, only if everybody works in the same time zone.
Even if you would think about also taking the time zone into consideration separately and create a custom calculation you would always have to determine the current Users Time zone as well. And how would you go ahead and display this calculation result in a column on the Schedule Board's Requirement panel? Maybe there's a trick with using calculated fields for it?
Oh man... especially in Schedule Board this is really disturbing that after years of Field Service Microsoft is still not able to provide a solution here and still have this column by default in their "Unscheduled Work Orders" view.
It's always helpful to bring these suggestions to the attention of the program managers. I didn't find any idea related to that topic, so I filed a new one, feel free to vote: experience.dynamics.com/.../
I am however pretty sure that this is a platform topic, not just a FS one, which means much more dependencies and complexity.
I agree with Alexander. Please bring these ideas up. Also understand that items are typically implemented (and I'm speaking on my own behalf, not Microsoft) if they benefit the entire platform, not just a few customers.
Business Applications communities