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

Deletion of created segment fails

SA-34190

Summary



After applying of HFix-28476, HFix-28466 and HFix-30624 users wanted to clean up the marketing application with removal of old segments created before applying the hotfixes. Deletion of segment fails with error message.

Although there are no campaigns making use of this segment.

Error Messages



This segment is currently in use by a running campaign and cannot be deleted at this time


Steps to Reproduce



1. Create marketing segment in designer studio (creation fails).
2. Apply HFix-28476, HFix-28466 and HFix-30624.
3. Delete marketing segment created before installation of hotfixes.


Root Cause



The query generated from Validate Delete activity was having incomplete columns to be fetched, hence was skipping from step 3 to step 12:

SQL : SELECT "PYCLASSNAME" AS "pyClassName" , "PYPURPOSE" AS "pyPurpose", "PZINSKEY" as "pxInsHandle" from <RULES_User>.pr4_rule WHERE ( "PYPURPOSE" LIKE ? ) AND ( "PXOBJCLASS" = ? )
SQL Inserts: <DF%> <Rule-Decision-DDF>


Resolution



Resave the segments created prior to the application of HFix's, so that the segment rules are re-generated and the query generated from Validate Delete activity is seen as:

SQL: SELECT PYCLASSNAME AS "pyClassName" , PYPURPOSE AS "pyPurpose", PZINSKEY as "pxInsHandle" from <RULES_User>.pr4_rule WHERE ( PYCLASSNAME = ? ) AND ( PYPURPOSE LIKE ? ) AND ( pxObjClass = ? )
SQL Inserts: <PegaMKT-Data-Customer-SegmentName> <DF%> <Rule-Decision-DDF>


Note: Delete the old segments.

Published March 13, 2017 - Updated December 2, 2021

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