Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Missing DSM simulation output properties value

SA-11466

Summary



User notices that not all properties value are recorded to the batch output. Some properties’ value are recorded as null, however, the property values are not empty in the final Strategy before recording the output to the database.

Local-change: Using Strategy to set the same property before the final public component invoked by the batch process. Basically just copy value from itself, that is, setting property value from property A to property A.

Error Messages



Some properties not being recorder for some offers, however, other offers might have all properties recorded.

Steps to Reproduce



Run the simulation test, with a import from named page.

Root Cause



The root cause of this problem is the smart fetch that is used with simulation run, as the process is trying to assign the value of same property to same property in the Strategy rule.

Resolution



Turning off smartfetching resolves the issue. The corresponding Dynamic System Setting is structureddata/enableSmartFetching.

Published July 27, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us