Extender Cascading Delete
I believe the feature you are looking for is already built into Extender and is called “Table Links”. You will find the setup for it on the Options button on the Windows Setup. It will allow you to link on specific GP tables that you want that particular Extender window to trigger off of to remove date. If the data is removed from the tables you add as links, then the Extender data for that record will be removed as well. It will remove it from the EXT01100 – EXT01114 tables where appropriate.
Here is a link to the section of the 2018 manual for Extender that talks about it. It is the same in 2013, 2015, and 2016 as well.
There is not a feature like this for forms as the forms aren’t linked to anything for us to trigger that removal off of. We could create a “clean-up” type maintenance window that would show you stranded records if you have the forms using lookups to GP data perhaps. I will enter that as a suggestion.
Excellent! Thanks, Nicole, I (obviously) didn’t know this lol. Off I go to do some linking!
Scenario: User is inputting a payables transaction. User adds Extender data. Before the transaction, the user decides they need more inf (say, vendor is not set up) , and “deletes” the transaction before they saved it. Transaction is gone, but Extender data is still there and will be used on the next entered transaction because that is the “last receipt number”.
I have looked, and can’t find a way to setup table links on TEMP tables (which is what I am assumed is being used while the entry is being made and before it is saved). Do you know how to set a table link to a temp table, or is it more advisable to change the business process (at which time the user enters the Extender info)?
I think I answered my own question: Change the process. Through monitoring SQL Trace, the TEMP tables are Global Temp Tables created on the fly by the GP process, and seem to change per entry (which makes sense).
For example, User 1 begins a transaction and ##2001231 is created, while User 2 begins a transaction and ##20011232 is created. There’s really no way to *easily* link temp tables, so this is an exception to the rule of cascading deletes.
The GP record must be SAVED in order for the Extender Table Links to function properly.
If you would like to submit an answer or comment, please sign in to the eOne portal.