UI Builder Filter component not compatible between Utah and Tokyo

[Ezhil45]

Using UI Builder Base Shell Page ive created a page with  Filter Component and some Data Visualization Components in my PDI Utah release. 

I tried importing this custom application in another instance on Tokyo and im seeing that the "Filter"  Component is not working as expected. It does not have any configuration that was associated to it.

When i checked for that page under "sys_ux_macroponent" i can see that the definition for that filter exists.

So i tried creating another filter and can see that the metadata/schema for the filter is different from what it is in "Utah" release. 

So does this mean "Filter" component is not backward compatible?  This would be a problem if i develop custom application  in one version and deploy it in customer instance in different version.  Can someone advise?

[Brad Tilton · Accepted solution]

Hi Ezhil, we try to make things forward compatible (if you build in Tokyo it should also work in Utah), but not backwards compatible. It's generally not a great practice to build something on a newer release and try to deploy to an older release. The main reason for this is that we might introduce something in a newer release that may not exist in the older release and result in that thing not working. Or we may change the way something works and support both versions in the newer release, but only the older version in the older release. This isn't unique to UIB and components, but true across the entire platform.

[Ezhil45]

Thank you @Brad Tilton . That Helps