web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Suggested Answer

BPF – Time/Timezone conversion issue when changing stage - Power Automate

(1) ShareShare
ReportReport
Posted on by 11

Hello everyone,

 

I’m facing a strange behavior related to time when using a flow to change stages in a Business Process Flow (BPF) in Dynamics 365 Sales.

 

I created a Power Automate flow to automatically update the BPF stage.

When I test the flow manually, everything works fine and the correct time is saved.

 

However, when the flow runs naturally (automatically by the system), the record is saved with a time 3 hours ahead of the real time.

 

Important: our organization uses the Brazil standard time (UTC-3).

 

It looks like a timezone/UTC conversion issue, but I haven’t been able to identify where this is happening.

 

I’ll attach a screenshot to better explain the scenario.

 

Has anyone experienced something similar or knows how to fix this behavior in Dynamics/Power Automate?

 

translate:



Any help would be greatly appreciated.

 

Thank you!

Categories:
I have the same question (0)
  • Suggested answer
    Tom_Gioielli Profile Picture
    2,995 Super User 2026 Season 1 on at
    Man, time zones and date/time conversions are just the worst.
     
    My guess is that when you run the flow manually, it is grabbing your own user timezone setting and applying the correct time for the save. However, when it runs automatically is maybe is grabbing the flow owner or authenticated connection user which has a different time zone setting?
     
    When you say the time is saved incorrectly, what exactly are we talking about? Are you referencing the [Created On] or [Modified On] field of the BPF record or a manual field/timestamp? When you are reviewing the date and time, are you doing it based on the flow run / database value / inside of CRM? Time zone conversions can happen in several places so it's important to understand where you are viewing and whether this is a system defined field (which would indicate an issue on the view side of the date and time) or a custom field (which would indicate an issue when setting the field value).
  • LA-03111723-0 Profile Picture
    11 on at

    Hello, thank you very much for your reply.

     

    Yes, the time zone conversion part is definitely tricky.

     

    In short: when I run a test inside the flow, the stage is updated correctly in Dynamics.

     

    However, my business rule is the following: whenever the Status field is modified, the process stage must also be updated automatically.

     

    In this scenario, when the Status is changed and the flow runs, it completes without errors, but the stage is not updated in Dynamics.

    I also noticed that, inside the flow, the timestamp appears to be using a different time zone than expected.

     

    Do you think I might be missing a configuration or action to ensure the stage is updated correctly?

  • Suggested answer
    Tom_Gioielli Profile Picture
    2,995 Super User 2026 Season 1 on at
    So the flow might run without error, but is it actually processing your step to update the stage? It's tough to know what might be happening without a full picture of the flow, but this is how I would run through this. Maybe some part of my process map would help here.
     
    Requirement
    • Upon changing of the [Status Reason] field on my primary entity called "Example Table", I want to update the related Business Process Flow stage to match accordingly
    • I'm going to assume that I have a single business process flow active on this entity/table, called "My Custom BPF"
     
    Basic Structure Approach
    Business Process Flow records live in a separate table than the tables they are related to. In this case, I should have a record in the "My Custom BPF" table that corresponds to a record in my Example Table. Because the Table > BPF relationship is 1 to Many, I can't use a D365 workflow to make the change. I'll need to use Power Automate (from what I can see, you are following along with all of this so far).
     
    The Power Automate Flow
    • Create a flow with the Dataverse trigger for when a record is modified in the Example Table. Limit the scope so this only runs when the [Status Reason] field is modified
    • Upon triggering, the flow will need to do a Dataverse List Rows action on the "My Custom BPF" table to find the exact business process flow that is related to my trigger record
    • I then will want to write a switch statement that checks what the new Status Reason field of the Example Table record is, and use that to define what the new stage should be in the Business Process Flow record
    • Finally, I will want to update the Business Process Flow record to the new process stage.
      • Important Note: The process stage in a BPF is a lookup field, not an option set or string field. This means we need to define the GUID of the process stage that matches what we want. The corresponding table name is something like 'processstages'
     
    Troubleshooting or recommendations
    • Make sure that your 'List Rows' action that is being used to find the BPF record is actually returning a row. If it is not, it might look like the flow is running successfully but it isn't actually ever updating anything
    • Check the timezone setting for the account in Microsoft 365 that owns the flow or that is used in the connection for your update row step, particularly if it is different than you own user account
    • Consider flipping this requirement around to simplify things. If you can make it so that you change the record status reason on update to the BPF flow stage, you can accomplish all of this in a D365 workflow that triggers on stage update in the BPF. Would only take a few minutes to accomplish
    If none of the above helps, posting your full flow with some details around your steps and actions might help diagnose a bit further where the issue lies. Hopefully something in here helps though!
     
     
    If this response helped, please consider marking as verified so future users can see the resolution. If you have additional questions or problems, please tag me in the response so I receive a notification.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 55 Super User 2026 Season 1

#2
Eugen Podkorytov Profile Picture

Eugen Podkorytov 49

#3
Jimmy Passeti Profile Picture

Jimmy Passeti 31 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans