Something changed on the AOT on version 19

(0) Share

Report

Posted on by AstridMalanka

Hi,

We have deployed version 19, and we saw one extended data type changed name, which is weird.

Here is the sample we found and I dont know if there is more. On the logistiPostalAddressBaseEntity, the field description, before the extended data type was called description, now it is called logisticdescription. Does it always happen? The changing of extended data type?

Also, after deployment we are finding the following error The data source is not embedded within a (parent) data source. On some forms. Is there anything we need to do? We have forms that are not properly working, and updating from excel is also giving errors.

Thanks

I have the same question (0)

All responses (6)

Answers (1)

Sort by

André Arnaud de Cal... 304,553 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Astrid,

Do you mean that on a specific column of the data entity the Extended Data Type property value was changed? This can happen, but will mainly not have impact on the behavior of the data entity. The EDT supports mainly the data type, field length and label. The length is not changed.

Can you provide examples how to reproduce your errors?

Was this reply helpful? Yes No
AstridMalanka 8 on at

Like (0)

Report
Copy link

Link copied!

I have duplicated an entity from sales order line, and we have a column there that is mapped to logistiPostalAddressBaseEntity - description (with the extended data type logisticdescription, the field is something like address description. (my dev environment is version 19)

when i committed my changes he couldn't build the model, not synchronize the database. (that machine was version 18), and after checking the error - that was pointing to sales order line missing logisticdescription as a extended data type, we compared the two version and we saw that in version 18, the extended data type has a different name.

once we updated that machine, we were able to build the model, and synchronize the database.

that is one issue. the other issue is that now, ODATA cannot find sales order line v2, and also we have an error on some forms saying "The data source is not embedded within a (parent) data source", and when they download an excel from one of those forms, they also get

I am told, nobody worked on sales order line entity.

Was this reply helpful? Yes No
Verified answer

WillWU 22,363 on at

Like (1)

Report
Copy link

Link copied!

Hi AstridMalanka,

This seems to be caused by the role names in the relations on data entity.

Here is a same issue:

community.dynamics.com/.../entity-relationship-salesorderlines-targetting-entity-salesorderline-not-found-on-entity-salesorderheaderv2

Was this reply helpful? Yes No
AstridMalanka 8 on at

Like (0)

Report
Copy link

Link copied!

I changed the name of the role and it didnt help, I tried to delete the role and then I also go error, my question is, what is the relationship for? do we need that relationship? thanks!

Was this reply helpful? Yes No
AstridMalanka 8 on at

Like (0)

Report
Copy link

Link copied!

There was more than one entity with issues.

Was this reply helpful? Yes No
WillWU 22,363 on at

Like (0)

Report
Copy link

Link copied!

Hi AstridMalanka,

Suggest you to raise a ticket to Microsoft.

Regards.

Was this reply helpful? Yes No