I would need a more specific example, but, I f I get it right, you could create a workflow associated to the object that you are importing that would run a QuickAction on the other object.
I have several hundreds of objects, which are periodically imported by file.
Already existing objects are getting updated, unknown objects are newly created.
Sometimes objects which already exist in Service Manager do not exist in the imported file, so I have to get them deleted or get a status like "inactive".
Hope that helps you to understand my problem.
2 of 2 people found this helpful
If you can have all your imports set a flag of some sort, like 'isImported', you could build a saved search to look for anything that doesn't have that flag. Updated items should get flagged as well a new ones, anything it doesn't touch won't have the flag.
If you really wanted them deleted, then just run the archive action in a workflow against that saved search. The WF can be set to run on a schedule, so you could have it run a little bit after your main imports
1 of 1 people found this helpful
That is a great idea! the workflow should remove the flag on the existing ones, so they are ready for the next import, but besides that, I think that your solution should work.
After some tests it seems to be enough to query "Modified On" as I let the import run only once a week.
I built a saved search "where %object% / LastModDateTime / Not Equal to / $(Today())
Then I created a scheduled job, running shortly after my import - as you told me
After following this HowTo How to link or associate a workflow to a scheduled job it did exactly what I want.
One thing was confusing: Using the Today() in my saved search told me that this function will be deprecated in a future release and to use BeginningOfDay() instead.
I did some tests with BeginningOfDay, but did not get it working, I think CurrentDate would be more useful, as it got the job also running
Thank you for your help!