Hi @KariB93WI I've attached the JSON of a scenario that may do what you're asking.   I've kept it generic and I use a naming convention for the TYAHs: field name = "tyah "+{name of the job role} That way I can identify which typahead to look for and I can do name matching between the TYAH field and ...

Hey @NickVa11 can you share the resulting JSON and/or error msg If the JSON has issues I often use tools like jsonlint to help me find the offending char(s) 

Hi @megkart This sounds interesting  So in theory: 1. get the project's resource pool and the pool's members 2. get each members availability and determine which are available enough for the assignment 3. iterate through the tasks and assign users   One challenge: defining "availability" - because ...

Ha! First legit and successful use of LLM!! I tried chatgpt (meh) and claude.ai (great) - I think I might begin using this going forward: you're a technical writer and will create documentationin MS Word based on an Make/Integromat scenario JSON the audience are business users who need to understan...

Hi @OmahaOmaha your requirement "80% identical title" needs to be refined. I would recommend not using a mutable string such as the title, but look at the project's fields (group, program, portfolio, enteredBy, status, priority, and any key custom fields) to ascertain whether the project is a duplic...

Hi @ChrisPerez I'm not clear on this use case and why you set up the store as you have. What's the input and the call to the datastore? 

Hi @BruceMe7  what you describe can't be done: Using an external lookup to drive display logic. To use display logic (ie hiding/showing fields based on the value of a field above them)  "you must add a radio button, dropdown, or checkbox field to the form anywhere above this form item."   Sadly an e...

Hi @AnnemarieWh Not sure if this helps - but I remember a weird issue where a form wasn't visible because it included a typeahead (in that case of programs).Do you have any typeaheads in that form? The Distributor Name maybe? 

Hey @NishaPatel Try this: Create a "report" report - a report of reports  and add a new column. In that column enter: linkedname=direct namekey=filter:definition querysort=filter:definition valuefield=filter:definition valueformat=HTML   You should get something like this  

Hey @JamesMa4 I didn't believe it at first but yes - that's a bug. [ When I toggle between new and old experience I also see different set of requests e.g. New: Filter - entered by me <=> Old: My requests ]Have you filed a ticket yet?