Hi team,
I am looking for a way by which I can delete a data from a data store entity having some conditions.
For example, I am having a cdt having the following structure and values,
ID - Name - email
1 - Jai - jai@vijay.com
2 - vishwaas - vishwaas@nahihai.com
3 - jignesh - jai@vijay.com
Now above, id is a primary key but I want to delete the data having email as jai@vijay.com
I am not able to achieve the same using a!deleteFromDataStoreEntities smart service. Can you pls help me in writing an expression rule which can delete the two rows (1 and 3 having email as jai@vijay.com)?
Consider name of the constant for data store entity as : myDataStoreEntity
Discussion posts and replies are publicly visible
You will need to first fetch the primary key values from that table using queryEntity, and then delete the rows based on that key.
could u pls elaborate ?
Yes
Could u please give an example, how can I write expression rule for the same (connecting with the appian cloud db) so that I can fire sql queries ?
You will find all the required details in the Appian documentation.
docs.appian.com/.../Query_Database_Smart_Service.html
you can use the Query database to delete the data from DB based on some condition.
use ac! to provide the value into filter and provide the value into Data tab on the smart service.
can we do it in expression ?
No. This is process only.
Its giving me a "Reaction Tree" as output. Also data is not getting deleted. What's the issue ?
deleteFromDatastoreEntities will work under save into configuration only.
I think we need a short intermission here. How much experience do you have with Appian, and what is your goal?
I am new to Appian Stefan.
OK. And what is your goal?
My goal is that, if someone clicks on a record name, then an expression rule should get executed which will truncate the table, here in the above scenario, I am trying with only 1 row for which the primary key is : 6722c859-76b4-4aa8-ac82-3b3f93f903ba
The trick with Appian is, that action does NOT happen within expressions typically. Records are your business data objects, and related actions implement certain activities. Use Interfaces for display purposes and expressions logic.
This will require a fundamentally different solution approach than you might be used to.
I am doing a POC for an application with Appian Stefan.
I found that I was missing onSuccess and onFailure attribute. It was so simple.
By the way thanks guyz for your precious time and efforts.