Question
CAPGEMINI AMERICA INC
US
Last activity: 5 Jan 2022 5:37 EST
Max Column length for pyLabel is 64 and updated in DB as 256, Still it is not allowing
pyLabel is already exposed and it is available in PegaCS-Specialization:08-01-01 Not able to update Max length and associated table already getting used. Updated Col Length in table but still issue occuring due to Ma length.
Performed restart and test connectivity and revalidation, But still issue not solved.
Please help if anything am missing for this kind of scenario.
ING Nederland
NL
@VENKATA_BHARGAVACan you check if this helps
https://collaborate.pega.com/question/pylabel-property-increase-max-length-128
Inovar
SA
Try saving the Data admin Db table instance for the class where pylabel column value is updated in DB.
Many a times after updating direclty in the backend table , need to update this instance.
Let me know if it still did not work.
CAPGEMINI AMERICA INC
US
@ArshadPashaMohammed yeah class instance is Data-Corr-Email which is not having any unlocked version, Tried to private edit the save button and removed visibility and saved the class instance. Still issue not resolved.
Inovar
SA
I mean Data-Admin-DB-Instance saving.
CAPGEMINI AMERICA INC
US
@ArshadPashaMohammed Yeah DB instance save and test connectivity performed. Still not resolved.
Inovar
SA
From PEGA when you check in database class mapping - is it showing the updated length value which you have exposed.
If yes , can you show case where the error is getting displayed with screen shots.