Hi All, i have a requiement to generate the .csv report of workobjects which are pendig status and where assigned to user or workqueue.
I am using RD created on work class and joined worklsit and WB provide the RD as source to the dataset, the problem here is if datasetCSV mapping rule , how to add the pxassignedoeprtorID property as its not work class property,
Tried to use the datatransfrom and passthe pzinskey to pxrefobjectkey and take that value one of the exisitng properties of the workclass and added that property the dataset but property is not holding any results.
The issue you’re hitting is that pxAssignedOperatorID is not a property on the Work class, it lives on the assignment-level class (Assign-WorkList or Assign-WorkBasket), so you can’t map it directly in a dataset that’s sourced from a Work-class RD unless you join properly and expose it through a Work-class property.
Using a data transform and pzInsKey → pxRefObjectKey is the right approach, but the reason your property ends up blank is usually one of these-
The join between Work and Assign-WorkList/Assign-WorkBasket is not correct or not evaluated in the context where the dataset runs.
The data transform is not actually populating the Work-class property in the same requestor/thread context that the dataset uses.
The dataset is not using the joined/derived property correctly in the mapping.
Usual pattern is-
Use a Report Definition on the Work class with joins (Assign-WorkList and/or Assign-WorkBasket) and use this RD as the source for your dataset. That’s the cleanest way to get a CSV report of pending work objects with user/workqueue assignment info.
I understand you’re working on generating a CSV report of pending work objects assigned to users or work queues, and you’re facing challenges with including the pxAssignedOperatorID property in your report.
Based on the context provided, here are some suggestions to help you:
Understanding the Class Structure:
When creating reports that combine data from multiple classes, you need to properly reference properties from joined classes. The pxAssignedOperatorID property belongs to the Assignment class (specifically Assign-Workbasket), not directly to the work class.
Proper Column Referencing:
When adding columns from joined classes in your report definition, you should use a prefix to identify properties from the associated class. For assignment-related properties like pxAssignedOperatorID, you would reference them using the appropriate prefix (such as pxWorkbasketAssignments.pxAssignedOperatorID).
Property Optimization:
For properties to be available in reports and datasets, they need to be optimized for reporting. This means they must be exposed as columns in the database table. You can optimize properties by:
Navigating to Records > Data Model > Property in Dev Studio
Searching for and opening the property you want to optimize
Clicking Actions > Optimize for reporting
Selecting the appropriate class and following the wizard steps
Class Joins in Report Definitions:
When you select properties with prefixes like pxWorkbasketAssignments, the system automatically adds an association rule to the report. This creates the necessary join between your work class and the assignment class. Make sure your report definition properly establishes this relationship.
Alternative Approach:
Instead of trying to copy the value to an existing work class property through a data transform, consider ensuring your report definition correctly joins to the assignment classes and references the properties directly from those joined classes. The join typically uses pxRefObjectKey from the Assignment class matched with pzInsKey from the Case/Work class.
Make sure your report definition’s Data Access tab is properly configured with the necessary class joins to access assignment-related properties.
Hi @ ravi - i am using the RD as source to the data set and joined the assignment classes to read the pxassignedoperatorID , when doing property mapping the dataset to generate the Csv , alias property is not an actual property on the work class it won’t take to map the property and there is no join opetion the dataset to generate CSV file
@sreenivasulur16806621 I can see the issue is with the mapping. In a Report Definition, joined-class fields are retrieved through the joined page structure, so the dataset mapping must reference the joined path rather than expecting pxAssignedOperatorID to exist as a direct Work-class property.
If the RD joins ‘Assign-WorkList’ or ‘Assign-WorkBasket’, the output row contains values from the joined class, but those values are not directly mapped into the base Work class automatically. So in the dataset mapping, ‘Assigned To’ should map to something like 'pxPages(Joined-Class-Prefix).pxAssignedOperatorID or the equivalent joined-page reference used by that RD result structure, not to a Work property such as .pyTempText unless you explicitly copied it there in a preprocessing/ post-processing step. If the data is not being copied into the Work page first, .pyTempText will stay blank.
