Personalized Community is here!
Quickly customize your community to find the content you seek.
Check out the latest Sales updates!Learn about the key capabilities and features of Dynamics 365 Sales and experience some of the new features.
Download overview guide | Watch Sales video
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
There is no OOB field property to show the time only part. If you are using date and time field, it can be configured as Date only or date and time.
Could you please explain your requirement in details.
There is a scenario where I have already created Visit Date and Time field for the client. But now the client wants two separate fields for Visit Date and Visit Time where they need this for the report purpose.
If this split up is required only for reporting purpose, you will be able to split the date and time separately on SSRS or fetch XML reports.
With calculated field its not possible to show time only part. you can use a plugin or workflow to achieve this.
Hope this helps.
Please mark as verified if this was helpful.
I was able to find the solution of this issue using Microsoft Flow. Will be happy to explain further if anyone need similar solution.
Thank you all for your quick responses and willingness to help.
You can share the details here so that it can help others as well looking for same/ similar scenario :)
Here is the solution I implemented
Scenario: A custom entity was having a DateTime field as input from various forms and APIs. Customer wanted to have separate columns for Date and Time for their internal reporting purpose. I found that Dynamics 365 is having Date as data type, but nothing for Time only. So I resolved to do a workaround as below
1. Created two additional fields as Date and Time on custom entity
2. Created a Flow triggering on Create and Update record on this entity
3. Split the DateTime field into Date and Time separately and assigned it the respective Date and Time fields.
4. Important thing to be noted here that when Flow pulls DateTime field, it returns data in UTC format instead of the tenant timezone. I used Convert Timezone action to change the timezone from UTC to tenant timezone before splitting the DateTime field.
Thanx Manoj. Yes, JS is an option but I found Flow as better situation in my scenario.
Glad you found the solution & it worked well for you
Business Applications communities