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

Database Table Class Mapping Issue



Users are getting errors in DatabaseTableClassMapping when they add the "." dot prefix to the property in the external mapping for the customer class (CustomOrg-CustomClass-Data-Customer).

When the "." dot prefix is removed from the external mapping user is facing the Segment issues.

Error Messages

pyPropertyName:This may only containes letters,digits,underscores and must begin with a letter.

Steps to Reproduce

1. Add the "." dot prefix to the property in the external mapping for the customer class.
Open the same class from the DataBaseTable Class Mapping wizard.

Root Cause

A defect in Pegasystems’ code or rules

In Pega 7.21 "." dot prefix is not needed in the external mapping and changes done in the external mapping would be reflected in the DateBaseClassMapping wizard, that is, if one adds "." dot to the property in the extrernal mapping it gets appended in DateBaseClassMapping wizard and error reported will be thrown.


The current release of Pega Marketing requires external mapping entries to be prefixed with a period.

This requirement is also mentioned in the Pega Marketing Implementation Guide.

User is requested the user to add the "." dot prefix to the property in the external mapping and ignore the error as it does not have a functional impact.

An enhancement request, FDBK-18755, has been created for consideration by Pega Product Management.

Suggest Edit

Published April 12, 2017 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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