Odd happening with Document IDs going missing between trigger and read modules! | Community
Skip to main content
S
stuartcairns
Level 4
June 24, 2021
Question

Odd happening with Document IDs going missing between trigger and read modules!

  • June 24, 2021
  • 3 replies
  • 1604 views

Hello all

I have a scenario that starts with an instant watch for new document versions being created. It gathers Version ID, Document ID, name etc. The next module gathers document-level data. The trigger runs ok and the version and document IDs are shown in the execution inspector but the second module fails saying the document ID doesn't exist. Also, when I use the document id shown in the execution inspector and search for that in Workfront, it's not found but when I use the document name from the trigger module, it is found, but it has a different document id to that shown in the execution inspector of the trigger module. My mapping of the document id from the trigger module to the read module is correct so I'm a bit stumped. Does Workfront do something odd with document ids in the background?

Thanks v much

Stuart Cairns

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

C
CiaranCa
Level 4
June 24, 2021

A couple of screenshots would be helpful, but if the documentID in the webhook doesn't actually exist when searched for, i'd double check the connections being used by each module, do you have multiple sandboxes/regions?

S
stuartcairnsAuthor
Level 4
June 24, 2021

Hi Ciaran. I've loaded some pictures, sanitised a little. I think it shows a clear story. I've put the screenshots in a word doc because I can load only a single doc into the record here.

D
darin_patterson
Level 4
June 24, 2021

Hi Stuart, thanks for those detailed screenshots. I apologize for the basic nature of this point, but are you positive that the first module is receiving events from the same instance that the 2nd module is interacting with?

I only ask because it's the only thing I can think of and I have been stumped by this myself once.

Doug_Den_Hoed__AtAppStore
Community Advisor
Doug_Den_Hoed__AtAppStoreCommunity Advisor
Community Advisor
June 24, 2021

Hi Stuart,

Following, interested, and as is Darin, puzzled. But I have another theory.

Where I would expect a drag-and-drop-new-version to keep the same Document ID before and after, what you're seeing behaves the way a delete-original-upload-new version...which would also then match the "version: 1" shown in your screenshot. If the intention of your scenario is to only capture new versions of existing files (i.e. the former), if you added additional criteria to exclude "version: 1" events of brand new documents automatically creating their corresponding initial version (i.e. the latter), I expect you would then remove the "noise" that we're observing.

If I'm following correctly that it is indeed the former you are after, would it then be possible to repeat your test, but include screenshots confirming the Document ID in production before (and after) initiating the intentional (e.g. "version: 2") drag-and-drop-new-version behavior...which I then expect will have the stable Document ID we all expect?

Regards,

Doug

S
stuartcairnsAuthor
Level 4
June 25, 2021

Hi Doug

Thanks v much for this. So you're theory is that the user is loading a document, thus creating V1 and then instead of adding a V2 they are deleting the V1 and then adding another version thus creating a new V1? Would that result in the original document id (as opposed to the version id) being deleted? V interesting theory. I'll definitely test that and post the results. I'm supposed to be not working today but I'm very curious so I'll see what I can do but it may be Monday before I post the results.

Thanks again

Stuart

Doug_Den_Hoed__AtAppStore
Community Advisor
Doug_Den_Hoed__AtAppStoreCommunity Advisor
Community Advisor
June 25, 2021

You bet Stuart,

Whether a user’s first deleting an existing file (to replace it), or simply uploading a new file, since Workfront will automatically generate a “version: 1” current version at that instant, with (yes) a brand new Document ID, theory such events are causing “noise” for your scenario (being focused on only “version: 2” or better, so my suggestion, if so, is that you skip such “version: 1” noise.

Regards,

Doug

Doug_Den_Hoed__AtAppStore
Community Advisor
Doug_Den_Hoed__AtAppStoreCommunity Advisor
Community Advisor
June 28, 2021

Huh: interesting one, Stuart.

Good luck with it, and I look forward to hearing how it turns out.

Regards,

Doug

Terms & ConditionsAccessibility statement

Loading footer...