Unanswered

Model driven app in managed solution is not updated after import of new version

(0) Share

Report

Posted on by mattiabergo

Hello,

I write because my company has got a staging environment and a production environment with managed solutions. My solution has got a model driven app, many flows and custom dataverse tables.

When I do an upgrade of the app in staging env. changing forms, the app itself and so on, and I publish everything, export and import as managed solution in the PRD env. the customizations are not shown.

Therefore, first thing I looked for, based on other forum cases similar to mine, is to check for customization layers into the prd solution, I looked for multiple layers in the Model driven app, on all flows, all tables, connections and forms, views. And no multiple layers, only 1 layer for everything.

I tried so to import the updated solution and on the import option I selected the "Update solution to the latest version, components not present in the latest version will be deleted" which is the standard option I use normally, but since it doesn't work I tried also the option "update the app, replace the previous version with the new one" but this is not working too.

What else do you suggest to try for this, avoiding to delete custom tables' data of the solution in PRD?

Thank you in advance!

Categories:

Governance & administering

I have the same question (0)

All responses (10)

Answers (1)

Linn Zaw Win 2,996 on at

Like (0)

Report

Usually, Upgrade is a recommended solution action during the import of managed solution. When you mentioned "since it doesn't work", does it mean the import was successful without any additional solution layer for the model-driven app but the changes are not reflected in Production environment? (or did you encounter any error?)

Was this reply helpful? Yes No
Verified answer

Parvez Ghumra 1,579 Moderator on at

Like (0)

Report

@mattiabergo I would suggest trying to import/upgrade the solution using the classic experience, this will enable you to choose the option to "overwrite unmanaged customisations", as long as you confident that you don't have any unmanaged cutsomisation in your target environment that you wish to retain

Was this reply helpful? Yes No
mattiabergo 17 on at

Like (1)

Report

@parvezghumra actually using the import in classic mode I can choose to overwrite unmanaged customizations.
This has allowed me to notice error logs that I didn't see before, including one that interests me:
Translated labels for the following languages could not be imported because they have not been enabled for this organization: 1040

In fact the customizations I was missing are the labels on the different sections and panes in the main form of a data table in the app.
I saw in the production environment the English language package is missing which in the staging I have, I asked the administrator to install it and then my problem was solved.

Definitely the classic mode of the import solution solves many issues that in the new interface are obstacles.

Thanks!

Was this reply helpful? Yes No
ashleymsteiner 12 on at

Like (0)

Report

Hello - I am experiencing a similar issue. I am trying to remove a section on a form. The change is unmanaged in Dev but am moving it to the UAT (staging) environment for testing. However, it is not being removed from the form.

I have tried to clone the solution and import into UAT with "stage for upgrade" and also used the "overwrite customizations" with the classic interface. Nothing is working to resolve this issue and the section still appears. I would really like to avoid having to make an unmanaged solution change to remove it.

Do you have any additional troubleshooting steps I could try?

Was this reply helpful? Yes No
Linn Zaw Win 2,996 on at

Like (0)

Report

@ashleymsteiner

Is it one of the OOB forms with a managed state in DEV? In the past, we had a similar issue where the changes that we imported were not reflected even though there was no unmanaged layer on top of it. Seems like merging the managed forms (the original managed form and the changes that we made) wasn't doing well. Ultimately, we resolved it by cloning the OOB managed form in Dev as an unmanaged form and modifying that form instead of the original one.

Was this reply helpful? Yes No
Parvez Ghumra 1,579 Moderator on at

Like (1)

Report

@ashleymsteiner I would strongly suggest comparing the managed layers on the form in question in your target environment and compare these with the managed layers on the same component in your source environment. If you see a difference in the number, combination or sequence of the managed layers between the source and target environments, you can be sure that this is the cause. Please report back with screenshots of the layers and I can advise accordingly thereafter

Was this reply helpful? Yes No
ashleymsteiner 12 on at

Like (0)

Report

@parvezghumra The source environment is an unmanaged environment, so the only solution layer is the unmanaged one. Please let me know if there is anything else I can check.

Was this reply helpful? Yes No
ashleymsteiner 12 on at

Like (1)

Report

@LinnZawWin The form is a copy of the managed form as I'm aware these issue can occur using the OOB managed form provided by Microsoft. In the source environment, it is an unmanaged form.

Was this reply helpful? Yes No
Linn Zaw Win 2,996 on at

Like (0)

Report

@ashleymsteiner

In that case, how many managed solution layers are there in the target environment? In an unlikely event, could there be any other managed solution layer on top of the one that you were trying to import?

While you are investigating it on your own, it would also be helpful to raise a ticket with Microsoft support in case they have solved similar issues before.

Was this reply helpful? Yes No
ashleymsteiner 12 on at

Like (1)

Report

@LinnZawWin There are a lot of managed solution layers as many people are developing in the environment. The layers are in the correct order. I've taken your advice and created a ticket with Microsoft Support. I will come back and share what the result is once we get it resolved.

Was this reply helpful? Yes No