Question
Vodafone
GB
Last activity: 8 Nov 2018 3:52 EST
pxPropertyName too long when optimising for reporting
Hello All
I am optimising a number of properties within our application and found that when I do an error is returned from within the activity Validate, Step 34 - Property-Set-Special. The error appears to occur as the propertyname that I am trying to optimise is greater than 64 charactors.
PropertyName - .ServiceInventory.EdgeServiceInventory.DSLServiceInventory.IPType
Is anyone aware of a way around this as we have built our data model in such a way that it fits our purposes for maximum re use. Is there a way I can expose this field without having to compromise the structure?
The best way to see this is to go to a concrete class,open the definition and add the column_name and property name manually, the error then appears at the top of the screen ans within tracer.
Kind regards
Andrew Lamey
Pegasystems Inc.
IN
Hi Andrew,
As you mentioned, I'm also getting error (maximum length allowed is 64) when added the column_name and property name manually under external mapping section in class definition.
But I tried to optimize the property with name more than 64 characters. The observation is - The property is optimized without any error. But the column name create in DB table is truncated.
I think this is related to database that we are using. I hope , this error is inclined to the size limitation of column name length with respect to DB type that we are using.
Please let me know if this helps.
Thanking you,
Venkat
Vodafone
GB
Thank you for your reply Venkat, please accept my apologies for taking so long to follow up myself.
The experiance I have is similar, the column is created in the database table no problem... however if I check the class definition > external mapping tab, the column name and property name is not there. Also, when I check the database table, although the column is there, the data is not.
If I check inside the blob I can see the data there, however it is not in the exposed column.
A check in the Column Population Jobs and I can see the job there, it has run, shows completed and with no errors.
It seems very odd that this would be a limitation