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

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Business Central flows...
Power Automate
Answered

Business Central flows don't trigger when moved to production

(0) ShareShare
ReportReport
Posted on by 55
We created a few flows that work fine when associated with our BC sandbox environment. We took these, performed a Save As, and redefined the environment name in those automated trigger steps. Same company name, just a change in the environment name. There were no warnings or errors when doing so. And the changes saved just fine.
 
The issue is that the production flows aren't triggered at all. For example, the first step of one flow is automated for when a new sales invoice is posted. Testing this out, the flow logs are still empty. I have seen cases where a typo in the company name results in an error. Since the flow step can't retrieve data from BC. In this case, no errors. Nothing at all.
 
This is a premium flow, and my user account that created it and manages it has a Power Automate Premium license. Running out of ideas about things to try....
Categories:
I have the same question (0)
  • Greg Kujawa Profile Picture
    55 on at
    I think I've narrowed it down. When I select the Cronus USA, Inc. company from our production environment, then the flow is triggered. The quirk must involve how the company name GUID is defined in both production and our sandbox environment. The sandbox is just a production restore, so the company's underlying ID GUID is the same.
  • Verified answer
    Greg Kujawa Profile Picture
    55 on at
    Figured it out. Basically quirky web UI in the flow designer. When it comes to the BC connector and the Planner connector, I had to keep pasting in the long ID's, saving the flow, and then I'd go back in and see the titles present in those fields. And the drop-down selector would finally appear. The BC company name, the Planner group ID, plan ID, and bucket ID all required this exercise. Now the flows work as expected.
  • Greg Kujawa Profile Picture
    55 on at
    Here's a vid cap of the behavior, and what it took to resolve this. Something inherently is the Save As function for a flow appears to affect the field values. Note the drop-down don't appear until I manually assign the internal ID's again. Definitely an odd ball.
     

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 Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the March Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Haque Profile Picture

Haque 592

#2
Valantis Profile Picture

Valantis 340

#3
11manish Profile Picture

11manish 284

Last 30 days Overall leaderboard