Powerautomate import flow error

[ct_klein]

Hello,

We have multiple environments (DEV/QA/PROD) that are identical except for the data.

I created a cloud flow in Power Automate and it works in the DEV environment.  I export it to a zip file and go to import it into our QA environment and I get the following error:

Flow save failed with code 'MultipleErrorsOccurred' and message 'The dynamic operation request to API 'commondataserviceforapps' operation 'GetMetadataForGetEntityCUDTrigger' failed with status code 'NotFound'. This may indicate invalid input parameters. Error response: {"error":{"code":"EntityNotFound","message":"Could not find table with name 'ct_plan'."}};The dynamic operation request to API 'commondataserviceforapps' operation 'GetMetadataForGetEntity' failed with status code 'NotFound'. This may indicate invalid input parameters. Error response: {"error":{"code":"EntityNotFound","message":"Could not find table with name 'ct_plans'."}}'.

The entities DO exist in the environment and I in the interest of time had to recreate the flow by hand.

Now I need to move the flow into our PROD enviroment and I get the same error message.

Any ideas?  I will create the flow manually again if needed but seeing has this is the first of what will be many cloud flows a more permanent solution would be better.

Thanks.

[LVanella]

I wish I had a solution, but can only say I'm faced with the same problem.

It's ridiculous that the data sources need to be identical in environments. They won't be anyway if you use Dataverse because of how the system adds a prefix. There's got to be some option to let us import the Flow cards as they are, even if they will need the source re-selected afterward.

[abdul_hadi]

any update on this so far?

[ct_klein]

Yeah, and it was a rather silly problem.  The entity that was part of the flow wasn't updated in the environment yet.  The flow referenced an new entity that was part of our build cycle but since I was trying to do the flow first it was trying to access something that didnt exist.  Once I figured that out and loaded the entity first, the flow imported without an issue.

[VijaySingh]

@ct_klein Can you mentioned the steps to solve this?

[ct_klein]

It wasn't a power automate issue as much as it was my user error.  I was trying to reference an entity attribute that did not exist yet in the environment that I was attempting to publish the flow into.  The flow was failing because its trying to use an attribute that it couldnt find.
Once I deployed the entity change to create the attribute, the flow imported properly.

[VijaySingh]

I am trying to get you. So I have table exist in source (let say ENV-A) which are mapped in flow, when I importing flow it is giving error saying Error response: {"error":{"code":"EntityNotFound","message":"Could not find table with name 'supplierproducts'."}} in ENV-B

I am assuming that I do not have table in destination ENV-B. So when I am trying to import the same my table name got change and it add some random character before table name. So I am trying to find steps to import it successfully. 

Flow save failed with code 'MultipleErrorsOccurred' and message 'The dynamic operation request to API 'commondataserviceforapps' operation 'GetMetadataForGetEntity' failed with status code 'NotFound'. This may indicate invalid input parameters. Error response: {"error":{"code":"EntityNotFound","message":"Could not find table with name 'supplierproducts'."}};The dynamic operation request to API 'commondataserviceforapps' operation 'GetMetadataForGetEntity' failed with status code 'NotFound'. This may indicate invalid input parameters. Error response: {"error":{"code":"EntityNotFound","message":"Could not find table with name 'products'."}}'.