Bionic Rule Not Pulling Specific Opportunity But Custom Rule Is

  • 15 August 2017
  • 4 replies

Userlevel 6
I created a Bionic Rule to first fetch data from the Opportunity object in SFDC and then to transform it and upsert into a custom MDA.

I noticed an issue when the 'Amount Closed' upserted into the MDA from the Opportunity object was not matching the amount from a report in SFDC . After some investigation, I noticed that there was one specific Opportunity not being pulled in called 'Upgrade - New Group Subscription'. As far as I can tell, it is still being marked in SFDC just the same as other Opportunities that are being fetched using the bionic rule. 

Furthermore, if I run a custom rule to fetch data from the Opportunity object using the same exact parameters and then upsert into the custom MDA object, I am able to pull 'Upgrade - New Group Subscription' in from SFDC and load to MDA just fine.

Not sure why the bionic rule is not allowing this? I have the same fields in the 'Show' section and the same Filters. I would assume that the Transformation task of the bionic rule is somehow causing this one opp to not be included..but my understanding was that the Fetch task should pull in all the targeted data and then the transformation would act on that data. So not sure why this would cause it to be filtered out.

Any help on this would be much appreciated! I have tried multiple different variations of the bionic rule and still not able to get that opportunity to load to the MDA object. 

4 replies

Userlevel 7
Manmeet -
This does sound strange.  Can you open a ticket with  
Userlevel 6
Sounds good, thank you!
Userlevel 2
Hello Manmeet,
Thanks for raising the issue. We have identified the root cause for this issue and fix is already being planned to be deployed. 
There are no changes required from your side on this. 

This issue was caused by  the special symbol " – " in the value "Upgrade – New Group Subscription". This a symbol is different from normal " - ". We have now added encoding support to address this issue. 

We will update you back on the support ticket once it gets deployed so that you can verify if it has fixed the issue. 
Userlevel 6
That's awesome! Thank you for the support!