Unanswered

365 Finance 'Update a record' action forcing me to try and update a read only field

(0) Share

Report

Posted on by J-G

134

I'm attempting to update some Fixed Asset records in our organization's finance module, but the update action has the 'Fixed Asset Group' field set as a required input for some reason even though it's not used for lookup. No matter what I put in there any attempt to run the action nets me a read only error, and I can't leave it blank because Power Automate insists it's a required field and refuses to save. Not even the results from a record load are letting me fill in the field successfully. Does anyone know how to get around this problem?

Categories:

Building flows

I have the same question (0)

All responses (6)

Answers (0)

Expiscornovus 33,195 Most Valuable Professional on at

Like (1)

Report

Hi @J-G,

In the past I have worked around this by using F&O API instead in a HTTP action. Have a look at these integration documents. For example OData supports CRUD.

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/odata

Was this reply helpful? Yes No
J-G 134 on at

Like (0)

Report

We currently can't access the database over HTTP and I have no idea if we'll get security access.

Was this reply helpful? Yes No
Expiscornovus 33,195 Most Valuable Professional on at

Like (0)

Report

Hi @J-G,

That is interesting, since the Power Automate connector is doing pretty much the same thing under the hood 😅

In the past we have worked around this by creating customizations in D365FO, but that required coding.

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/develop-entity-for-data-migration

Was this reply helpful? Yes No
J-G 134 on at

Like (0)

Report

I'll take a look at that, thank you. Do you know anything about why Power Automate is forcing me to update certain fields? I don't understand why that would even be a feature.

Was this reply helpful? Yes No
Expiscornovus 33,195 Most Valuable Professional on at

Like (1)

Report

Hi @J-G,

Because certain fields are required in the data model for certain entities. In the interface you would have form logic and business rules which would work differently. That's why sometimes data integration can be a bit more challenging compared to manually form input.

Was this reply helpful? Yes No
J-G 134 on at

Like (0)

Report

But the action is only used to update existing records which would logically already have that data if the creation process followed the model's rules (and the contents of those fields outside of read/write access would be irrelevant regardless because it's an update action). It just seems like a strange design feature to me, but there's nothing you can do to help that.

Was this reply helpful? Yes No