Data transform only works if it is checked out

Blueprint and App Design
, , , ,
1

I have a data page that calls a REST service. The service has a request and response data transform to map the parameters in and the responses received. If I have the response DT checked out, it works fine. If I check the response DT in, it fails with the following errors:

PRRuntimeError:
Failed to compile generated Java com.pegarules.generated.model.ra_model_runhistoricalsearch_response_5c9f2169090f359194d70ad1b7956238: Annotation processing got disabled, since it requires a 1.6 compliant JVM

  1. ERROR in /com/pegarules/generated/model/ra_model_runhistoricalsearch_response_5c9f2169090f359194d70ad1b7956238.java (at line 78)
    actionProlog(pz_CurrentTraceInfo,“1”, “Append and Map to”, pz_3, targetProperty_1);
    ^^^^
    pz_3 cannot be resolved to a variable
  1. ERROR in /com/pegarules/generated/model/ra_model_runhistoricalsearch_response_5c9f2169090f359194d70ad1b7956238.java (at line 119)
    actionEpilog(pz_CurrentTraceInfo,“1”, “Append and Map to”, pz_3, targetProperty_1);
    ^^^^
    pz_3 cannot be resolved to a variable

2 problems (2 errors)
Compile failed.

I can re-create the issue over and over by just checking in (fails), check out (works), discard changes (fails). I even tried creating an entirely new data page and DTs all with different names, but that does exactly the same thing and gives the same error message.

I found reference to this article (https://community1.pega.com/support-articles/page-set-data-transform-does-not-work-when-rule-checked) which was marked as the solution in this similar question (DataTransform is NOT executing when the Rule is Checked in | Support Center) unfortunately the link to the article is broken so it’s not very helpful.

Any suggestions would be greatly appreciated. Thanks.

2

@IanB5391 Ok, so I’m going to just make my silly mistake public in case it helps somebody else out. One of my DTs was referring to a property that was accidentally created in another branch. So the DT worked if I had it checked out but once it was checked in, it was no longer able to access the property in the other branch. A quick Save As into the proper branch fixed it up. Cheers.

3

@IanB5391 Thanks for posting this. I was also facing the same issue. And after doing a lot of research found your post. It helped me solve my problem too :slight_smile:

4

@IanB5391.. thanks it helps to understand where I did mistake for same issue :slightly_smiling_face:

5

@IanB5391 Thanks for posting this. I was also facing the same issue, after adding the property to current branch, it solved the issue