Parameter value is not passed correctly to source Data Page in a View-based application

General
1

Hi everyone,

I’m facing an issue with parameter passing to a Data Page used as the source for a dropdown in a View-based application.

Here’s my setup:

  • I have a Text property named Branch in the class Common-LDM-Entity-TransactionModule.
  • This property is displayed as a Dropdown in a View.

image
image347×371 12.5 KB

  • The dropdown values are populated from the Data Page D_TransactionModule_List (Common-LDM-Entity-TransactionModule).
  • The Data Page requires a parameter (Branch) to retrieve the correct list of values.

image
image662×821 24.6 KB

  • The parameter value should come from pyWorkPage. I can see that the value exists on the clipboard.

image
image591×208 14.4 KB

The issue is:

  • If I hardcode the parameter value in the source Data Page, the dropdown works correctly and displays the expected values.
  • However, when I configure the parameter to use the value from pyWorkPage, the parameter is not populated correctly at runtime, and the Data Page does not receive the expected Branch value.

Has anyone encountered this issue before?

  • Is there any limitation when passing Data Page parameters from a View-based application or Search Group configuration?
  • What is the recommended way to pass a property value from pyWorkPage to the source Data Page of a dropdown?

Any suggestions or best practices would be greatly appreciated.

Thank you!

2

Can you please check with Top.Branch or Primary.Branch to pass the parameter?

3

Hello @Eranda_Weerasingha

  1. You can try putting it as Top.TXnSearchBranchCode rather pyWorkPage.
  2. If this does not work then create a property on the Common-LDM-Entity-TransactionModule class level named “TxnBranchCode” and create a declare expression for the same property to return @pxParentProperty(“TXnSearchBranchCode”). This should return your parent level property value in embedded context.

Below are some useful OOTB functions which everyone can use for this kind of multi-level context data access.

image
image514×257 5.67 KB

Let us know the outcome. Hope this helps.

Regards

JC

4

Thank you for your suggestion. @JayachandraSiddipeta and @RameshSangili

I tried all the approaches you mentioned, including using Top.TXnSearchBranchCode and Primary.TXnSearchBranchCode creating a TxnSearchBranchCode property on the Common-LDM-Entity-TransactionModule class with a Declare Expression using @pxParentProperty("TXnSearchBranchCode"). Unfortunately, neither approach worked in my case.

I was able to resolve the issue with a different approach. I added the TXnSearchBranchCode property to the View, set its default value from the corresponding work-layer property on the clipboard, and marked the field as Visible = False. Once the property was available in the View context, I used it as the parameter for the source Data Page, and the dropdown worked as expected.

This solution resolved my requirement. Thank you again for your suggestions.