Notifications

21 views

Description

Symptoms


Tab in PA dashboard moving back to default name after renaming it.

 

 

 

Cause


This issue can happen if there is corrupt data in the language field for user trying to rename the tab.

Any value other than the correct language represented by to first letters can cause this issue.

You will see the following error when you debug.

FAILED TRYING TO EXECUTE ON CONNECTION 2: INSERT INTO sys_translated (`language`,`label`,`sys_id`,`name`,`value`,`element`) VALUES('NU','TABNAME1','f03a83efdb0ba344779fe665059619bd','pa_tabs',TABNAME1','name'),INSERT INTO sys_metadata (`sys_replace_on_upgrade`,`sys_mod_count`,`sys_updated_on`,`sys_class_name`,`sys_id`,`sys_package`,`sys_update_name`,`sys_updated_by`,`sys_created_on`,`sys_name`,`sys_scope`,`sys_customer_update`,`sys_created_by`) VALUES(0,0,'2019-01-23 09:26:40','sys_translated','f03a83efdb0ba344779fe665059619bd','global','sys_translated_f03a83efdb0ba344779fe665059619bd',JOHN DOE','2019-01-23 09:26:40','TABNAME1','global',0,'JOHN DOE') 
java.sql.BatchUpdateException: Duplicate entry 'pa_tabs-name-TABNAME1' for key 'name_2' 
: java.sql.SQLException: java.sql.BatchUpdateException: Duplicate entry 'pa_tabs-name-TABNAME1' for key 'name_2': com.glide.db.StatementBatcher.getSQLException(StatementBatcher.java:494) 
com.glide.db.StatementBatcher.commitBatch(StatementBatcher.java:449) 
com.glide.db.StatementBatcher.commitAllOrNothing(StatementBatcher.java:330) 
com.glide.db.DBCompositeAction.executeAsBatch(DBCompositeAction.java:193) 

Resolution


Go to the sys_user record for the user.

Add language in the form view and change it to en (whatever valid language in two characters).

 

 

Article Information

Last Updated:2019-08-02 20:54:09
Published:2019-01-25