Question
Sopra Steria
FR
Last activity: 20 Aug 2018 8:41 EDT
Method Apply-DataTransform cannot be performed on a symbolic Page name: Primary
Hello,
In an activity, I am looping on a Page Group property of my Work Object.
In this loop, I wish to apply a Data Transform on my Work Object. My initial idea was to apply the Data Transform on Primary to be in the context of my Work Object and not in the context of my loop.
Doing that, I have the error "Step page— Method Apply-DataTransform cannot be performed on a symbolic Page name: Primary" when Saving.
The only workaround we found was to Property-Set a parameter to @PrimaryPageName(tools) and pass it as the step page of Apply-DataTransform.
Is there a proper way to pass the primary page to the Apply-DataTransform ? Why is the use of Primary proibited ?
Thanks
***Edited by Moderator Marissa to update platform capability tags***
Pegasystems Inc.
FR
Hello.
I don't know the exact reason but the error message is quite clear.
I believe your local change is the right one to use.
Pegasystems Inc.
GB
Urgh. Not sure why you can't do that; and (with all due respect) that Work Around is horrid. (I mean -it's actually brilliant - but you shouldn't have to do that....)
I'm not sure *why* you cannot use a Symbolic Name for a Step Page here...seems that it would fit to me ?
But I don't know : so I logged a BUG on this (BUG-390801 : "Apply-DataTransform cannot be performed on a symbolic Page n...) - so this will give our SMEs the chance to review whether this is something which *has* to be the case, or whether it should be handled in a different way , or whether it doesn't need to be the case etc....
This is unlikely to result in a HFIX (assuming that this is indeed the way it *has* to be..) , but it might end up being fixed in a later version of PRPC (assuming it doesn't have to be this way)...
Sopra Steria
FR
Haha, thank you for your answer, I will forward the "horrid but brilliant" part to the perpetrator of this workaround :D
Is there a way to keep track on the bug evolution ?
Pegasystems Inc.
GB
Hi Patrick,
I believe you can request about BUGs etc via your Pega Account Manager; as far as I know there is no published list of pending BUGs etc.
I hope the 'horrid but brilliant' Local Change is sufficient for you at this time.
Some other things to try (I have *not* tried this - and they might not work) - and maybe you have already tried these ?
1. Leave the Step page blank - would this still give you the correct context ? (I'm thinking it might not, depending on how your Activity is called....)
2. Set the Step Page on the step *prior* to the APPLY-DATA-TRANSFORM....(again, I haven't checked, but does this keep the same context from the prior step ?)
3. Create a dummy LOOP (which 'iterates' just once) - place the Primary Page on *that* step, but leave the Step Page blank on the APPLY-DATA-TRANSFORM step (which should be sub-step of the loop).
Thanks
John
Pegasystems Inc.
GB
Yup - I also confirmed the situation. I logged the BUG in order for this to be looked at by our SMEs.
(I'm not sure if this is something that has to be the case [and if so, perhaps could be handled in a more friendly way?], or something that can be altered to allow 'Primary' in the Step Page).
Pegasystems Inc.
IN
Yeah thanks for your response, with this we can achieve but what our concern here is why its throwing error when we give step page as Primary.!