Hi @TraKill If I understand this correctly, you're populating the dropdown with 32 entries (30min) per day, for every work day?  How do you populate this?  Also, not clear on this bit "the RECORD TYPE FORM or FIELD does not exist in the dropdown" - what do you mean?    as for "hide a field choice" v...

What does "closing out" mean - did these projects just not get closed due to human error? And the approvals were given but the user(s) didn't click "Approve"?Then Kristen's approach is short and sweet - you'll just need to distinguish between project/task and issue approval.  You'll also need to see...

I like this @FrankatMSC because it removes any guessing. 

Hi @FrankatMSC When you do the search for documents, look for documents where opTaskID (and taskID) is blank. If it's not blank the doc is attached to a request (or task).  If both are blank it's attached at the project. 

Hi @Stacey_Robertson I'd create a ticket - that seems off they chop off the value portion due to a "("   Meantime, roll your own with a regular expression (Match Pattern module) IF all your key-value pairs are on separate lines:  ^(\w[^\n\r:]+:\w.+?)$ [ \w = a-z and A-Z and 0-9 and _ (underscore) ] ...

Can't tell from here. It sounds like there is an iterator that goes over all assignments, does some work, and ends in the create-record module.    Original response:  get assignments based on projectIDget the user/team assigneddeduplicate the result Make sure you're doing the saearch with a customAP...

Hi @BrownPaperBag what shows up with decimals -  related to grouping? or the actual records? 

Hi @NCorver the search module is a "user friendly" module - and no you couldn't search by that. You'll need to use the customAPI module. In the module you'd add query arguments to match you search.   Note if you need to you could add another level  {parent}.{parent}.{parent}.{parentID}  

Hi @NCorver Thank you for sharing! So I see two ways:  in your search, if you use the custom API module, you can say e.g. parent:parent:name = XYZ OR:1:parent:parent:parent:name = XYZAdd a hidden (admin only) calculated field to the grandchild/great-grandchild tasks with the correct parent IDIF(ISBL...

Can you use the get/pick() function? also - try to first set a variable to {{28.`DE:....} that would be the "eval" step