I have data page defined at our application framework level which fetches list of reason codes (MyOrg-FW-SampleFW-Data-Reasons) . Now, we are adding two more implementation for which the reason list is different. I tried overriding the data page to divisional level so that I can change the type specific to new implementation class (MyOrg-myDiv-Sample-Data-Reasons) and getting below warning.
A data page with this name already exists with a different type. This may result in unexpected behavior at run-time. Consider renaming this data page.
Is there a better way to implement the requirements?
Is it only a naming issue? Instead of "overriding the data page to divisional level", what if you make a new data page with a different name at the division level. It seems unlikely you'd still get a message saying "A data page with this name already exists with a different type".
I believe that, the new implementation class (MyOrg-myDiv-Sample-Data-Reasons) will be directly inherited from the FW (MyOrg-FW-SampleFW-Data-Reasons) Class. Instead of overriding data page, override the Source of Data page like data transforms, Report definitions or Activities in the respective layers to populate the list based on Application.