Errors after upgrading to 10.0.44 from .40

(1) Share

Report

Posted on by Johnny

6,466

Hello,

currently we are on V40 on our Live system.

We upgraded two of our Dev machines with Service / Quality update 10.0.44.

LCS installation went without problems.

After that, we just logged in to our Dev machine and did the Build of our Custom modules and it ended with multiple hundrends of strange errors.

For example, most of the error messages are, that some table / fields / classes could not be found, etc..

e.g. many many errors are "Table XXX does not contain field named YYY", which isn't correct.

The References between modules are correct and we can 100% see that in the AOT we see the elements that the error messages say could not be found.

So, something happened during the upgrade.

Has anybody have similar problem after any upgrade?

Thanks.

Categories:

Dynamics 365 Finance

All responses (6)

Answers (1)

Adis 4,457 Super User 2025 Season 1 on at

Like (2)

Report

Errors after upgrading to 10.0.44 from .40

Hi,

"But I could not find online, or in MS docs that those classes are removed and what we should use instead of them?" - very good question.

I would reach out to MS via Ticket.

Kind regards, Adis
Verified answer

Jonas "Jones" Melgaard 4,122 Super User 2025 Season 1 on at

Like (0)

Report

Errors after upgrading to 10.0.44 from .40

My immediate assumption is that they should return true, since the feature should be always enabled now.

So, remove the enabled() checks, and remove the feature class check.

However, after you have fixed the compilation errors.... Have a look in the standard application to quickly verify if you should make additional changes to your code. You should be able to find the affected areas by doing a cross-reference check of the feature classes in a developer environment with 10.0.40, and then see if you can identify affected areas in 10.0.44.
Johnny 6,466 on at

Like (0)

Report

Errors after upgrading to 10.0.44 from .40

Hi Jonas,

you are right. I just saw that those classes exist on V40, but on V44 not anymore.

But I could not find online, or in MS docs that those classes are removed and what we should use instead of them?

Thank you
Suggested answer

Jonas "Jones" Melgaard 4,122 Super User 2025 Season 1 on at

Like (0)

Report

Errors after upgrading to 10.0.44 from .40

The class InventJournalWorkflowApprovalFeature and ReqPriorityBasedPlanningFeature does not exist in 10.0.44, so that might the culprits.

Try to out comment the class (If possible) and remove the feature class references and see if it at least cuts down on the number of compilation errors.

As said, compilation errors can cascade. So a compilation error in model 1 might make it so that no artifacts can be seen when compiling model 2, making the number of compilation errors explode in the development environment.

On a side note, using feature classes can be very problematic as Microsoft might remove them if a feature gets defaulted on.
Johnny 6,466 on at

Like (0)

Report

Errors after upgrading to 10.0.44 from .40

Hi Jonas,

Thanks for the reply.

No, the fields are not moved to another model.

For example, the error described above is following:

Our partner company has created the custom model (Model1). there they have created extension of PurchLine table and added field YYY.

Model1 has not be modified at all for the last 8-10 month.

Then we have internally created our own model, let's call it model2, which is referencing to model1.

In our Model2, we have created new Data entity where one of the datasources is the PurchLine and we use the extension field YYY in the data entity fields.

This data entity has also been created few month ago.

Now after upgrading the dev machine from LCS to V44 and doing the compilation we have many similar errors. Or errors that some classes could not be found.

For exmaple.. one of the errors is also pointing to MS 'feature' class. The error message is "The name 'InventJournalWorkflowApprovalFeature' does not designate a class or table".

This one 'InventJournalWorkflowApprovalFeature' as I know is so called 'Flight', and can't be found in AOT anyways, right? This Feature class is also used in Model1 as "if (InventJournalWorkflowApprovalFeature::enabled())".

I have also copied and edited our build pipeline and configuered it with Nuget packages of V44.

When I run the pipeline it ends only with 15 errors.

From this 15 errors, 13 is "The name 'InventJournalWorkflowApprovalFeature' does not designate a class or table".

And remaing 2 are also same "AxDataEntityView/Model1_PurchPurchaseOrderLineV2Entity/Fields/PlanningPriority/FeatureClass - Class 'ReqPriorityBasedPlanningFeature' does not exist.".

So.. by running the Build from pipeline, it seems that the references are not a problem, but running the Build from dev machine Visual Studio, it seems to be a issue, even though I can conform 100% that all the references are in place.

I don't really understand what the problem is and how to solve it.
Jonas "Jones" Melgaard 4,122 Super User 2025 Season 1 on at

Like (0)

Report

Errors after upgrading to 10.0.44 from .40

I've seen something like this before. A version upgrade caused a compilation error that cascaded to other models that in turn also got a compilation error.

I wonder if something similar is happening for you?

Alternatively, can you see if the fields Dynamics is complaining about has been moved to another model? Maybe it's an issue with referenced models.