Error in the update set logs after committing the update set

[Karun Thej]

HI,

Getting the below error in update set logs after committing the update set in production. Didn't get this error while deployed in Test env. 

Log : Cannot invoke "com.glide.db.PrimaryKey.addQuery(com.glide.db.meta.Query, String)" because "this.fPrimaryKey" is null

Could you please let me know why this error occurred and what impact will it create in instance.

Thanks

@Community Alums @Dr Atul G- LNG 

[Dnyaneshwaree]

Hello @Karun Thej ,

I think that, there is some data related to the table record which required unique identification is required for your current configurations present in the your current update set. That was already present in the test invironment so, no issues occured but not present in prod. Please check the difference between test and prod for related all configurations.

[Richard Hine]

I have also had this issue in a PDI when committing an update set, did you get to the cause?

[John Brown2]

I have submitted a case to HI Support for this issue as we just had it.

[Sudeep5]

Could you please check the scope of all the customer updates in the updatesets is in same application scope. I have seen these issue when there is scope mismatch.