To prepare for upgrade from 8.5.5 to 8.7 we received a clone environment for testing.
Unfortunately manual import to a data type is not working. I created a test-csv having semicolons as separators. When starting the import the clone environment will not separate the records. It seems that it does not recognize the semicolon. Importing the same file to our existing environments is working without any problem.
I raised this as a ticket INC-217159 14 days ago and added the testfile as well as hardcopies from staging clone and staging environment. But beside of the triage I got no answer / no reaction at all from pega support. Maybe there is somebody in the community willing to help me.
@MichaelK1674 your issue does indeed require further investigation by means of a support incident.
I checked INC-217159 and indeed progress has been a bit slow.
I have chased this up for you in the relevant team and have been notified that an engineer will be in touch soon.
@MarijeSchillern
Giving an update as the problem may arise for any user working with the locale de_DE.
The Decision Table CL: @baseclass ID: pzGetLocaleListSeperator RS: Pega~RulesEngine:08-07-01 has been changed. An entry has been added for de_DE which was former not in place giving the wrong separator komma instead a semicolon. Before there was no entry for the language code de and the otherwise-branch was used giving the correct separator for germany.
Unfortunately I am not aware how to change a rule which is marked as [Final; Internal]. We will not be able to upgrade to 8.7.1 until this problem is solved.
@MichaelK1674 I can see that the investigation in the support ticket is ongoing.
If the issue has arisen due to an change of functionality between versions, or an undocumented update step in the product then I would expect our support department to continue to investigate and help you remedy the issue in such a way as to bring both environments to work as expected.
Please do keep us posted.
@MarijeSchillern
We started on Pega Version 8.1.4 and hat updates to 8.3.x and 8.5.x. Until now we did not face this issue. As far as I can see the decision table has been changed in Pega~RulesEngine:08-07-01 and delivered to us in the staging-clone.
The same problem may arise for anybody upgrading to 8.7.x and having operators using the locale de_DE.
For our installation the issue is followed up by Pega support in an incident. Therefore you may close this question.
@MichaelK1674 many thanks for your update.
I can see that the support lead is trying to avoid any issues for future clients by raising this issue with our engineering team.
The support ticket will remain open and I will update this thread with any findings that come our way to satisfactorily document this issue within the OOTB product.
@MichaelK1674
Thank you so much for keeping us abreast of the situation. I’m sorry to hear that there was no alternative apart from using the workaround to temporarily alter users locale using pyPreCSVUpload & pyPostCSVUpload activities.
I’ve checked the engineering ticket and indeed within the product that is the only fix they can suggest for you at this time as there is indeed no other way to alter the [Final] pzGetLocaleListSeperator decision table.
I have attached the Bug reference to this forum post so that we can track when the issue will be integrated within the next Patch Update (possibly 8.7.4/ 8.8).
For reference: BUG-721071 logged against Manual import of csv-files
“pzGetLocaleListSeperator” decision table is returning comma for separator instead of semi colon. Fix in future versions will be to change the seperator from , to semicolon.
Are you happy to mark this as the Accepted Solution within this forum question?
The result from the SR as final update from my side:
…
The issue has been investigated by the SME who concluded that there is unfortunately no workaround apart from the one already provided.
Additionally, the issue has been raised as a Bug in the Pega code.
As for the suggested workaround the pyPreCSVUpload & pyPostCSVUpload (part of Rule-Decision-DecisionParameters).
The two metioned extension point activities within the csv upload execution should allow to temporarily set the pxReqLocale property on the pxRequestor page.
…
