Skip to main content

 –

Creating a data type when sourcing large data pages from a connector, activity, or data transform

Suggest edit Updated on November 9, 2021

To source large data pages from a connector, activity, or data transform, define the fields that you want to include in the data page by creating and configuring a data type.

  1. In Dev Studio, create and configure a data type:
    1. Create a data type that you want to use for your data page.
      For more information, see Creating a data type in Dev Studio.
    2. On the Data model tab, click Add field.
    3. In the Add field to dialog box, enter the name and type of the property that you want to include in the data page.
    4. Optional: To add more properties to the data type, click Submit & add another.For example: For an Expense data type, add the following fields: Title, Description, Amount, Currency, and EmployeeID.
    5. After you add all properties to the data type, click Submit.
    6. Click Save.
  2. If the source of the data type is local data storage, ensure that you optimize the pyModificationDateTime and pyIsRecordDeleted properties by performing the following actions:
    1. On the Records tab, create a dedicated table for the class by clicking Configure source.
    2. In the source list, add the pyModificationDateTime and pyIsRecordDeleted properties by clicking the Plus icon and selecting the corresponding property names.
    3. Click Submit.
    4. In the Review dialog box, confirm the settings by clicking Close.
    5. Click Save.
    For more information about property optimization, see Planning for property optimization.
What to do next: Create and configure a data page that you later declare as large. For more information, see Creating a data page when sourcing large data pages from a connector, activity, or data transform.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us