You are viewing limited content. For full access, please sign in.

Question

Question

Cloud WF - Removing Fields from Unassigned Template Doesn't Work

asked on September 8, 2023 Show version history

Piggy-backing this thread; but didn't want to dig it up.

Cloud WF: Remove Fields from Unassigned Template Doesn't Work - Laserfiche Answers

 

I'm having this issue with some improperly assigned documents while importing.  With some testing, it seems that it's just the EMAIL based fields that aren't removed.

Other fields seem to be able to be unassigned as the template is set to blank.

 

I have this in a recursive workflow that I tested ability to assign a dummy template, then re-ran to remove the template and unassign fields and it works... with the exception if I added an EMAIL based field. *this workflow was only being used in a test folder; will have more conditions before I push through the repository.

Fields that remain, and won't unassign

 

Thoughts from the experts?

 

*Edit
Further to this, I can run a search with some filters, select the documents (with the email template) and then unassign the template and the fields are removed too.

It's just 7000+ within a main folder that I noticed the issue... so was hoping for an easier solution to get them all 'reset' without having to select multiple groups, as selecting over200 items at a time in cloud to retrieve the fields takes a bunch of time.

0 0

Replies

replied on September 8, 2023

Okay - Seems like I may have figured out my issue.

 

When I first ran the WF I may have had the checkbox to "remove fields from unassigned templates" unchecked.  Then when trying to run the WF again with the checkbox ticked, it wasn't working... because the template was already removed.  With the template already set to none, the fields would remain as they're not associated with anything.

Staring at things too long can be a bad thing.. cool

Seems to be working properly now though.  Carry on!

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.