Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
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 ?
Hi, could you please show me the record image?
I have used the data store entity instead of record
6722c859-76b4-4aa8-ac82-3b3f93f903ba is this the primary key value?
OK. And what is your goal?
yes,
6722c859-76b4-4aa8-ac82-3b3f93f903ba is the primary key
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
Is the entity which you are taking is correct?
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.