cannot compare record across environment. In one or more environments, the record does not exist or you dont have sufficient privilege in DEV environment

There could be the following reason due to which the error is coming

1. The record might not exist in one of the environments.
2. Even though you are part of the admin groups, there could be hidden permission restrictions.
3. Even though you recreated the table, there could be discrepancies in database schema like the data source can be different.
4. Sometimes, Appian caches old metadata, leading to inconsistencies in object comparison.

To debug the error, I would suggest, we can try the following:

    Verify Record Existence:
        Run a queryRecord() for that specific record in expression in both DEV and QA environments to confirm the record actually exists.
        If using a Record Type, check if the source data is correctly mapped in both environments.

    Check User Security in QA Again:
        Go to Record Security and verify access for your user.
        Try accessing the record directly (via a related action or record link).
        If it fails, there might be an issue with data-level security rather than object security.

    Manually Delete and Re-Deploy:
        In QA, manually delete the record type.
        Redeploy the record type without the data first and then deploy the data separately.

There could be the following reason due to which the error is coming

1. The record might not exist in one of the environments.
2. Even though you are part of the admin groups, there could be hidden permission restrictions.
3. Even though you recreated the table, there could be discrepancies in database schema like the data source can be different.
4. Sometimes, Appian caches old metadata, leading to inconsistencies in object comparison.

To debug the error, I would suggest, we can try the following:

    Verify Record Existence:
        Run a queryRecord() for that specific record in expression in both DEV and QA environments to confirm the record actually exists.
        If using a Record Type, check if the source data is correctly mapped in both environments.

    Check User Security in QA Again:
        Go to Record Security and verify access for your user.
        Try accessing the record directly (via a related action or record link).
        If it fails, there might be an issue with data-level security rather than object security.

    Manually Delete and Re-Deploy:
        In QA, manually delete the record type.
        Redeploy the record type without the data first and then deploy the data separately.

Hi sharma_kapil Thank you but we tried all the above mentioned steps. Everything works fine in both DEV and QA seperately. UUID of the record types are also same. No record security imposed. Also tables are deleted along with record type in QA and recreated table from dev and moved recordtype from dev again. Even in Dev we removed the recordtype that had issue and updated it with the new record type pointing to same table still issue persists.

I was going to say that perhaps there was an issue with Record Security since there was a mention of data in the error message.

• What's the name of the Record, any chance you're using some sort of reserved keyword?
• Are you sure that your deployment account is an admin?

Yes Mathieu Drouin . No reserved keys. Deployment is done by admin only. We didnt get any issue for other record types. But only one of these landed up with this issue.

Hi aishwaryaa913655 ,
Can you compare the  table structure  within the database as well ?

Yes sharma_kapil  We checked. The table structure looks fine. We deployed same table to QA.

Hi aishwaryaa913655 ,

Please check with the environment security / Reord security, deployment user must be in admin console for both environments.

Hi Varun Teja Gurrapu Yes the user is in admin console for both environments. We are able to deploy other objects. Only this record has this issue.

Can you check whether the use comparing these records have underlying Data store security in both the environments. 

No it remains same for all records on both environment. Actually I tried to duplicate the record and found that one of the grid fields in the list was giving this error. I tried to add one grid field at a time and found the fix. Thank you all for your inputs!