Merging customized layers with changes to base layer after upgrade

Currently on 2023.2 and testing 2025.2. I am reading the What’s New in 2025.2 guide and testing the new features and noticed that my customized layers do not contain the changes made to the base layer. For example, in PO Suggestions, a new view filter was added to include Requisition List. I can see this on the base layer, but not my customized layer.

My concern is, if I hadn’t read the patch notes I likely would have not noticed this addition. What’s the best practice right now for merging these changes? I assume something in my customization is causing this, because I thought base layer changes would still apply to the customized layers.

Am I supposed to be rebuilding every customized layer from scratch on each upgrade to remove the chance of any new features not appearing?

In theory, when you send a MetaFX SaveApp call to the server, on the back end the server is doing a diff vs. the base form, and only changes are saved.

With such a large version discrepancy since you created the layers, it is likely that something got saved into the layer which is overriding the new addition (if the new addition is a child of a parent object that you modified, your parent object modification might override all children)

You’d have to take a look at the base layer json and your customized layer json in to suss out where the gotcha is.

No, you aren’t supposed to rebuild every layer from scratch on each upgrade, but gotchas like this can happen.

2 Likes

Thanks, I will look into that. Also just discovered the compare tool on the version history in App Studio, but this doesn’t seem that great.

I can understand that these things just happen and most of my customizations may not have similar issues, but my problem is I have no way of really knowing if there is a problem with my customized layer or a new feature is being hidden. This example in PO Suggestions didn’t show any warnings or errors at the bottom in App Studio.

1 Like