@DavidRoss91 Thanks for raising this.FYI .. I know both the Product and Engineering teams are working on different tasks to improve the filtering, I've added your comments and a reference to this post in one of our internal reports for visibility.
Currently, the Computed Attribute feature does not support fields based on the `relationship` XDM construct.If using one of those, you will get a 500 error upon publishing Why is this feature important to you:Ability to use relationship exists at schema level, you'd want to be able to leverage this ...
@hariprasathg note there is a limited Data Lifecycle Beta in place whereby you can create requests to delete records based on their primary identities .. from a single dataset or all datasets.[...] delete data from the Identity Service, Real-Time Customer Profile, and the data lake
@andreacastillom apologies I hadn't seen your ping. I'm afraid these are typical support ticket issues for which our Support engineers would be looking in the logs for additional info, hence difficult to answer in a forum post.If you still face the issue, please make sure to raise a support request ...
@Shafiqur while I'm not here to prioritize these ideas/feature requests, I know this has been reported internally already as well as by some of our other customers. I've added a reference to your post in our internal notes. Hope fully that helps in the long run. Thanks for posting!
@Ananthan_Jayagopal & @Anuhya-Y the request here is really about having the on-demand evaluation feature we have in the APIs as a UI feature:
On-demand evaluation allows you to create a segment job in order to generate an audience segment whenever you require it. Unlike scheduled evaluation, this ...
The single click (with a confirmation dialogue) is still quite risky in a production environment probably why we don't offer this straight from the UI so having a smaller set of people doing these tasks through the API / BAAAM is safer.That being said I see the pain point, good 'idea' to make on thi...