Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Delete App Subscription data in ACS

rajdeepk3961735
Level 2
Level 2

All Campaign User,

Can anyone please suggest how to delete data from mobile app subscription schema in ACS.

"Mobile app subscription" schema is not being displayed under identification table (dimesion to delete) in the 'update data' activity.

I am flitering  the records form 'profile schema' in Query activity follow by using 'Update data' activity to delete those records from "app subscription" schema.

Any suggestion oo help would be highly appreciated. Thanks!!

1 Accepted Solution
Adhiyan
Correct answer by
Employee
Employee

Hello Rajdeep,

The Deletion of the appsubscription table via a workflow is not possible in ACS as of now. The table can only be read from the workflow.

In case you want to delete a custom attribute (column) added as an extension , you can delete it from Administration > Development > Custom resources and then publish the changes .

Regards,

Adhiyan

View solution in original post

4 Replies
florentlb
Level 10
Level 10

Hi Rajdeep,

I am not sure this schema is designed to be visible. Some technical schemas are kept private or are read-only to avoid problems in case of direct update/delete. What exactly would you need to delete?

Florent

rajdeepk3961735
Level 2
Level 2

Thanks Florentlb for the reply.

I want to delete custom attribute which are added to app subscription schema as part of extension schema.

Adhiyan
Correct answer by
Employee
Employee

Hello Rajdeep,

The Deletion of the appsubscription table via a workflow is not possible in ACS as of now. The table can only be read from the workflow.

In case you want to delete a custom attribute (column) added as an extension , you can delete it from Administration > Development > Custom resources and then publish the changes .

Regards,

Adhiyan

View solution in original post