I am running a flow to create new records in the Common Data Service (CDS) and yes, I know it is Data Flex Pro now :).
The problem is that if I set a Date Field on an entity it is not setting to current
Date from Account entity:
Date on new record when I set the value like the following (the Package Begin Date from the Account entity) and this field is defined as "Date Only".
On the create you can see it is setting to the 8/1 date but with a UTC time and no timezone offset. This field is also a "Date Only" field on the entity.
It seems like I have to do a lot of work here just to set one date field to another date field across two entities correctly. Does anyone have thoughts here?
Solved! Go to Solution.
Not fully understood your issue here. I can see the dates are mapped correctly which is 2020-08-01. Did you tried to retrieve the date from Account Package Services and see if values are showing any different or not?
I suppose you want to know how to manipulate values of ind_packagebegindate and ind_begindate because of the value differences.
You can try to use formatDateTime expression convert a datetime to a specified format and manipulate the values.
The date on the entity for the newly created record is set to 7/31/2020 vs. 8/1/2020. This is the issue I am having... I am doing no calculations at all, just taking the date from the Account record and storing on the new entity and they are both defined as Date Only fields. The Account's date shows 8/1/2020 while the newly created record shows 7/31/2020.
So we are in central time zone, are you saying I need to use formatdatetime on every date I am working worth and make sure I am setting the field with the timezone offset for Central? Can you give me an example what you would do in this situation?
Thank you, I will utilize these functions to accomplish as this is what I have been doing because there was no option. Overall I see this as a bug since I am taking a Date Only field from the instance and mapping it directly to another date only field, there should be no reason that I have to do this conversion on creation of the new record.
I would suggest you raise a ticket to Microsoft Support if you really have concerns of the datetime value to confirm whether it's a product issue or due to some configurations. If it's a product issue, Microsoft will fix it in the future release.
Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.
Watch Nick Doelman's session from the 2020 Power Platform Community Conference on demand!
Check out the community blog page where you can find valuable learning material from community and product team members!