@Andy_Wroe Thank you so much for all your help. We believe, we cracked the mystery behind why the decision diamond is failing with dropdown fields.
As you know our dropdown field values are ‘No’ or ‘Yes’. With default being No, the field values will show No in the UI interface by default. We made the assumption that because the UI always showed the default value of No on all areas of Infusionsoft that the proper value of “No” was also represented in the database backend. This appears to not be the case.
Our decision diamonds were initially designed based on “If the Field equals No” to enter the sequence because the UI shows No, but the decision diamond failed. We started to explore if the default value in the database table for the dropdown field is No(0)? or is it Null? We now believe that no matter if the contact is created before or after the custom field was created, each contact record is initialized with something like NULL, even though the UI is showing No everywhere.
As a quick test we changed our decision diamond logic to “If the Field does not equals Yes” instead of Equals No. To our surprise, all the contacts went through the decision diamond exactly as we had expected. So now we see our assumption that the default value in the database table is not No (0) but something else.
We tested the behavior with a new custom dropdown field with default No with existing contacts and new contacts created after the field is created. We designed decision diamond with rules Equals No, Does Not Equal Yes , Equals Yes, Does Not Equal No.
Contacts with default field values entered both ‘Does not equals No’ and ‘Does Not equals Yes’ sequences which proves us that the default value is something other than Yes or No like Null.
We were initially very confused as to why the Actions / Test on the decision diamond worked exactly as we expected, yet the contacts did not follow the logic as we had tested. This further confirms that the contact database field is initialized to something like Null.
We are glad for the road block being cleared now. Hope this might help someone.