ConfiForms IFTTT Rule not updating filtered record

[Jonathan Creech]

I am having trouble with my IFTTT rules in a form for the ConfiForms add-on. They were working the previous day and stopped working today. As far as I can tell I have not changed anything that would prevent the rules form working.

Below is source code for a simplified version of my page. I have a field, ProductName that is updated in a Registration Control on another page and that creates the initial project record. Then on another page I use a registration control form to update PMRProductName and NewData. The first IFTTT updates the initial/original record based on filtering to ProductName. The second IFTTT then deletes the newly created. The second IFTTT rule is working, but the second one is not. Any help would be greatly appreciated. 

<p>
<br/>
</p>
<p>
<br/>
</p>
<ac:structured-macro ac:macro-id="703c3205-182b-46fc-aa0d-5f3b3b53fead" ac:name="confiform" ac:schema-version="1">
<ac:parameter ac:name="formName">ConceptForm</ac:parameter>
<ac:parameter ac:name="debugMode">true</ac:parameter>
<ac:rich-text-body>
<p>
<ac:structured-macro ac:macro-id="440e8e31-0066-47af-b4b5-6a6d61ce55c5" ac:name="confiform-field-definition" ac:schema-version="1">
<ac:parameter ac:name="fieldName">ProductName</ac:parameter>
<ac:parameter ac:name="fieldLabel">Product Name</ac:parameter>
<ac:parameter ac:name="values">[92179579|ProductProjectTracker|ProductNameFill|true|false|]</ac:parameter>
<ac:parameter ac:name="extras">false[]</ac:parameter>
<ac:parameter ac:name="fieldDescription">If product name does not exist, select OTHER to enter new product name</ac:parameter>
<ac:parameter ac:name="type">smartselect2</ac:parameter>
</ac:structured-macro>
</p>
<p>
<ac:structured-macro ac:macro-id="86b7c16f-83fd-46a0-870f-6a29eb947213" ac:name="confiform-field-definition" ac:schema-version="1">
<ac:parameter ac:name="fieldName">PMRProductName</ac:parameter>
<ac:parameter ac:name="fieldLabel">Product Name</ac:parameter>
<ac:parameter ac:name="values">[92179579|ProductProjectTracker|ProductNameFill|true|false|]</ac:parameter>
<ac:parameter ac:name="extras">false[]</ac:parameter>
<ac:parameter ac:name="fieldDescription">Type or select the project name from the list. If it does not already exist in the list, click Report Issue above and provide details. </ac:parameter>
<ac:parameter ac:name="type">smartselect2</ac:parameter>
</ac:structured-macro>
</p>
<p>
<ac:structured-macro ac:macro-id="3bf46467-f298-4fe8-9017-721c90cb6583" ac:name="confiform-field-definition" ac:schema-version="1">
<ac:parameter ac:name="fieldName">newdata</ac:parameter>
<ac:parameter ac:name="fieldLabel">New Data for Product?</ac:parameter>
<ac:parameter ac:name="values">false[1=No new data|2=New data set|3=New source for existing data set|4=Adding new fields to existing data set|5=Disclose formerly internal only field|6=LN as a Reseller|]</ac:parameter>
<ac:parameter ac:name="extras">id;false</ac:parameter>
<ac:parameter ac:name="fieldDescription">Is there new data being added to the product. Either new data field, set or using existing internal only field?</ac:parameter>
<ac:parameter ac:name="type">select</ac:parameter>
</ac:structured-macro>
</p>
<p>
<br/>
</p>
<p>
<br/>
</p>
<p>--updates original ProductName record with the fields from the PMR checklist so that they are in sync with one another on a single record. </p>
<ac:structured-macro ac:macro-id="c45d6592-6508-464c-9a1a-78f75de4c4d3" ac:name="confiform-ifttt" ac:schema-version="1">
<ac:parameter ac:name="condition">!PMRProductName:[empty]</ac:parameter>
<ac:parameter ac:name="action">Update ConfiForms entries by filter</ac:parameter>
<ac:parameter ac:name="event">onCreated</ac:parameter>
<ac:parameter ac:name="title">PMRProductName=[entry.PMRProductName]&amp;newdata=[entry.newdata]</ac:parameter>
<ac:parameter ac:name="extras2">ProductName:[entry.PMRProductName]</ac:parameter>
<ac:parameter ac:name="who">ConceptForm:92179579</ac:parameter>
<ac:rich-text-body>
<p>
<br/>
</p>
</ac:rich-text-body>
</ac:structured-macro>
<p>
<br/>
</p>
<p>--deletes the newly created half record that we do not need because of the above update to the original product record. </p>
<ac:structured-macro ac:macro-id="28f7b153-ccaa-4ea3-98ce-51a1fba7eda6" ac:name="confiform-ifttt" ac:schema-version="1">
<ac:parameter ac:name="condition">!PMRProductName:[empty]</ac:parameter>
<ac:parameter ac:name="action">Delete ConfiForms Entry</ac:parameter>
<ac:parameter ac:name="event">onCreated</ac:parameter>
<ac:parameter ac:name="title">id:[entry.id]</ac:parameter>
<ac:parameter ac:name="extras2">ProductName:[entry.PMRProductName]</ac:parameter>
<ac:parameter ac:name="who">ConceptForm:92179579</ac:parameter>
<ac:rich-text-body>
<p>
<br/>
</p>
</ac:rich-text-body>
</ac:structured-macro>
<p>
<br/>
</p>
<p>
<br/>
</p>
</ac:rich-text-body>
</ac:structured-macro>

[Jonathan Creech · Accepted solution]

Hi @Alex Medved _ConfiForms_ ,

Here is a better explanation through pictures of the edit screen. 

Below is the Form

Below is the First IFTTT that should be updating the original record created on registration A when ProductName and PMRProductName match on the record created from Registration B. This is the task that is not working. 

[Alex Medved _ConfiForms_]

Sorry, I am still confused... PMRProductName and ProductName are smart fields and they reference same form, with same mappings... is that right?

What do you update here!? a field "newdata"?

This is what I see when I test it - http://recordit.co/R7tRFZp3Ac

And it works exactly as the IFTTT rules tells it to work

[Jonathan Creech]

It turns out that when I switched the second smart drop down to refer the first, it broke the IFTTT record update and even if I switched back it remained broken. Once I reverted to a version of the form from a week ago, I was able to iterate to point where it broke. 

[Jonathan Creech]

@Alex Medved _ConfiForms_ 

Tagging you because you were so helpful last time. Any help would be very much appreciated.  

[Alex Medved _ConfiForms_]

You say

" The second IFTTT rule is working, but the second one is not. Any help would be greatly appreciated. "

Not sure I understand what is not working and what are you trying to achieve