Declare Expression Not Function For Localization of Report Definition column heading.
We want to automatically change the title of the Report Definition depending on some date property.
As a possible solution, we assumed that we could put a variable in the Field value's translation and change it by a Declare Expression when referring to that field value.
It is translated by Field Value in the item on a page screen, which proves the implemented Declare expression works correctly.
I also confirmed that the translation destination of the Field value of the Report Definition title could be translated with a fixed value. However, the Declare Expression does not work when changing the title of the Report Definition. Via some investigation by the GCS engineer, it looks like this is an expected OOTB behavior.
For column value localization, we can only set a localized text. The property used in the field value we set needs to be on pyReportContentPage. Since this page gets formed through code, the property will always be blank in the context of pyReportContentPage. I hope we can make it enhanced in our product.
***Edited by Moderator Marije to add Support Case Details; ***
***Edited by Moderator Marije to change Type from Question to Discussion and added Idea tag***
Updated: 11 Apr 2023 10:24 EDT
Pegasystems Inc.
GB
@tongk could you clarify - is this a product enhancement request?
Please could you provide the INC reference where this issue was investigated?
In order to provide some context it would help if you could provide screenshots and a clear business use case for our SME' to look at.
Updated: 11 Apr 2023 10:24 EDT
Pegasystems Inc.
JP
@MarijeSchillern Thank you for your response. You can refer to INC-260196 for details regarding this symptom, but not much investigation info is left on this case.
The message below is what I got from the GCS engineer. She told me I should post my request here for product management to review and consider taking the feature in.
----
This is an expected OOTB behaviour. For column value localisation, you need to set a localised text. The property used in the field value that you are setting needs to be on pyReportContentPage. Since this page gets formed through code, the property will always be blank in context of pyReportContentPage
Updated: 11 Apr 2023 10:24 EDT
Pegasystems Inc.
GB
@tongk thanks for the ticket reference relating to 'Declare Expression Not Function'.
However I am unable to see the exact response which you have quoted. Can you please provide the date that the engineer posted that comment in the support ticket?
From what I can see the the logged question was and there was very minor investigation as they determined that your question was a 'how to' question.
The additional info you were given:
"This is an expected OOTB behaviour. For column value localisation, you need to set a localised text. The property used in the field value that you are setting needs to be on pyReportContentPage. Since this page gets formed through code, the property will always be blank in context of pyReportContentPage"
--> This shows that it is how the product behaves.
The behaviour is documented in our guides : Field Values and in our academy training : Design considerations for localization
@kamav can you confirm that there are no plans to change the OOTB localization functionality in the near future?