By using this website, you agree to our Terms of Use (click here)
I am trying to delete vendor prices (AP202000)and vendor details from the stock items (IN202500).
There are quite a few so it needs to be done in bulk.
How do i add a Delete action to an export scenario for this type of data? The regular <Action: Delete> is not available in this case.
Alternatively, can this be done via GI with ability to delete records?
Hi Ellie,
This is a good question, but unfortunately I don't know how to do it. I've deleted header records before, but you need to be able to delete detail records which I don't know how to do yet.
If i had this problem, I would start with working out how to create an import scenario that could update those rows that you want to delete. This is covered in I100 Integration Scenarios training (look at 2.5.2 and 2.5.3). Then i would export those rows that I wanted to delete. Then in my import scenario, instead of doing any updates, i would just trigger the relevant Delete Row action (using the exported rows for the import).
Thanks Royce, i have done all that already.
I have an import and export scenario. I can even mark them as 'inactive' etc. but i can't figure out how to apply the delete row action. Acumatica doesn't seem to give the delete option in import and export scenarios on the detail level, it only works on summary level.
Any ideas about that last delete step
?
You're right. It doesn't allow you to call delete actions. Now I see the problem 🙂
How about publishing a DB script to delete the data via SQL? Of course you need to be really careful before doing this in your production environment.
I guess that is what we will have to do as a last resort....
Ironically, I just discovered today that the delete action on a Sales Order Line is not available in field level security. I have a feeling that the two things are related since it's missing in both places.
Ironically, I just discovered today that the delete action on a Sales Order Line is not available in field level security. I have a feeling that the two things are related since it's missing in both places.
I wonder whether Delete action is directly tied to Access Rights on the object? So if a user gets Edit or Insert access, Delete action is disabled. If they get Delete access, Delete action is enabled. Maybe Acumatica thought they were being smart by directly linking some objects to Access Rights.
Yea it is any Grid /Details rows.
We opened a case with Acumatica support. Ill report back:)
The Acumatica response will be interesting on this one.
Finally heard back.
You setup a key field to let the system know which line to delete ( '@@FiledName' accomplishes this)
Then on the next line, map to =-2 , which is the same as clicking on Delete Row button
Adding a screen shot of a working import scenario that deletes vendor prices for illustration which can easily be applied to all similar situations for anyone who can use it.
Not sure how that happened... thanks for pointing that out.
I don't see an option to edit the old post anymore, so here is the correct screenshot:
Awesome! Thank you for sharing. I don't see though the <Line Number> =-2 in your screenshot. Am I missing something?
Wow this is great news. I don't remember seeing <Line Number> = -2 to delete a row documented anywhere.
Wow, that second screenshot is not what I was expecting. Great to have this on file for the next time I need to do something like this.
Maybe add a Blog so it's easy to find?
Will be even better when a GI can be used as the source and then you just need to setup your criteria in the GI and the matching data gets automatically deleted.
As in, the 1st item listed here:
https://www.augforums.com/augforums/everything-else/acumatica-2019-r1-new-features/#post-2963
As in, the 1st item listed here:
https://www.augforums.com/augforums/everything-else/acumatica-2019-r1-new-features/#post-2963
I hit reply to @timrodman when asking what was anticipated. sorry for the confusion. now i know to use quote instead of reply if i am responding to an earlier message on the forum.
You can't delete in destination with help of export scenarios. It is not very hard to program such logic, but negative results will be much more then positive. Consider following use case: destination database has records, that come from two different sources: from Acumatica, and let's say from Salesforce. And if you want Acumatica to delete something at destination, you'll need to inform Acumatica to delete some records, but if you'll not be careful enough export scenario will delete other records which were brought by Salesforce.
From that standpoint if it is needed to make synchronization of data between Acumatica and some custom destination I prefer to add some custom logic, that deletes data each time user clicks on delete button in Acumatica.