Updating default vendor bank using Power Automate requires changing user's default legal entity

(0) Share

Report

Posted on by M Christopher

We are using Power Automate to update the default vendor bank accounts across several legal entities. The primary key contains the correct legal entity id but regardless, the system seems to have an issue if the users' (the person running the power automate script) default legal entity does not equal the one identified in the primary key.

We have a work-around to first change the users' legal entity default first and then running the update script. But this doesn't seem intuitive to me.

Can someone confirm if this is by design or if there is a more correct way to do this without having to change the user profile settings?

Appreciate any insight into this. Thanks.

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

nunomaia 25 Moderator on at

Like (1)

Report
Copy link

Link copied!

Power Automate D365 connector connects using user company, defined in settings.

A workaround for that, is to connect by using Power Automate HTTP connector.

You can submit an OData request and you can define company there.

Was this reply helpful? Yes No
André Arnaud de Cal... 303,669 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi M Christopher,

Nuno provided a workaround. I wrote a blog about this topic before and reached out to Microsoft. They mentioned me that it will not be changed and that you can setup virtual entities in Dataverse and use the Dataverse connector.I haven't tried it myself. The suggestion from Nuno would be quicker as it would not require additional virtual table setup.

Was this reply helpful? Yes No
M Christopher 52 on at

Like (0)

Report
Copy link

Link copied!

Thanks. Will give those a try.

Was this reply helpful? Yes No