@Gopika_gp - ensure you do not have any unmanaged layers in your production solution. If you have any, please delete them.
If you do not have any unmanaged layers, you now need to directly open the production version of the canvas app
and identify what is causing the error with your variable.
It is possible to edit a canvas app deployed into a production environment as part of a managed solution by accessing that app directly from the Apps section.
Once you open the app in edit mode, the data source pane will still "display" as if it is still pointing to your DEV/UAT data source, but you can rest assured when looking at the data, the canvas app is actually looking at your PROD data. This is a defect Microsoft are aware of with environment variables deployed across different environments in a Solution.
https://learn.microsoft.com/en-us/troubleshoot/power-platform/power-apps/solutions/dataverse-environment-variables
Note that any modification you make, save, or publish will not impact the canvas app hosted in the managed solution. No unmanaged layers will be created in the Solution.
Regarding the error. The error is appearing because you’re populating a variable with a record which contains a specific schema, but then somewhere else in your app, you’re also populating that variable with a record which has a different schema.
Some classic checks
If you’re using an Edit Form control, it is important to understand that an Edit Form contains two important properties, the DataSource property and the Item property (which is used to display a specific record).
The schema used in the DataSource property, and the schema returned in the Item property must match. For example, suppose you’re populating the Item property with a Gallery selection (or a variable created from a Gallery selection), if the data source used in the Gallery Items property is different than the data source used in the DataSource property in the Edit Form control, you will receive an error.
This occurs very often when users leverage the AddColumns or GroupBy function when modifying the Items property of a Gallery control. If you have modified the schema of the Gallery like this, then the data source used in the Gallery Items property, and the data source used in the DataSource property of the Edit Form, will no longer match.
To accommodate for this, it is best to use a LookUp function in the Item property of the Edit Form. For example:
Lookup(yourdatasource, ID = Gallery1.Selected.ID)
Or if using a Variable:
Lookup(yourdatasource, ID = MyVariable.ID)
If your scenario matches the above description, it is important to restart the app after you make this correction in order for the error to disappear.
Other checks
- Ensure you do not have a Global Variable and a Collection with the same name.
- Follow a process of elimination to identify which variable declaration is causing the error. For example, navigate to the variables menu to view how and where the variable is being defined, and then for each declaration of that variable:
- Delete one instance where the variable is being being declared/initialised.
- Click save and restart the app and check if the error still appears.
- If the error continues to appear, repeat for the next variable declaration and keep restarting the app.
- Once the error disappears, you can then pinpoint exactly which declaration was causing the error, and then investigate further.
