I’m try to pass in custom attribute a parameter, using Param Page.
Yet, trying doing something like that doesn’t work, when retrieving the json of the I got a 500 error.
Using the tracer I receive this message:
The page or property Param is read-only, and cannot be modified. Calling method: PageDirectoryImpl.getPage Details: reserved page named ‘Param’ does not exist and cannot be created
I do not want to edit, I just want to show.
The parameter is defined at section level (is passed from another section, since the one in which I’m inserting the Custom Attribut is an embedded section.
So I’m asking: is Param supported in DX API? Or there’s no way to pass into json the param element?
@DanieleD9965 If data page is using Report definition or other data source make sure “use parameter” page is checked on the DP data source parameter popup to pass through the URL parameter to the data source.
In general DX API attributes are used by customer components to add behavior not found in the OTB Pega UI model provided by DX. Any Pega OTB use of DX API attributes are name prefixed by a ‘$’ character. Given custom DX API parameters are free form name/value pairs used for any purpose, data page parameters is one possible use, unless OTB starter kit component was modified to use the customer specific DX API attribute it’s ignore by OTB starter pack components.
is Param supported in DX API? Or there’s no way to pass into json the param element? Really three questions:
Does DX API support passing section parameters?
Does DX API support resolving param.MyProperty references for a specific component? Please share which component is using the param.MyProperty syntax. Any changes made to the OTB component?
Does DX API support resolving param.MyProperty references to it’s contained value in DX API Attributes? Though without customer changes to starter pack component DX API attributes aren’t automatically used by OTB Starter Pack components.
@DanieleD9965 Hi, At present the DX API V1 does not support property references for Param (param.property) or Page (page.property). Only references relative to pyWorkPage (ie, .property or.page.property, etc.) or a data page (D_page or Declare_page ).
My Idea was to give a dynamic parameter to the third part interpreter. In this particular case was the index of a nested list, that was passed as Parameter in section. Since as Paul told, this is not supported, I just found another way. I passed an hidden element in the external section, with the pxListSubscript, in this way I do not use the Param.parameter.