Recently while trying to filter combo box Items we were getting the values but it was coming as blank instead of showing the name field.
Below is a sample Form – connected to Leads and Source Campaign is the combo box field (lookup to Campaign)
As we can see without applying the filter we can see the name (Display fields) populated.
Now let us try to filter it based on the Campaign Type field.
Here we have applied a single filter condition.
We can see the combo box getting filtered correctly.
Now we are introducing a variable just to filter it based on condition.
Till now filtering works as expected.
Now let us introduce else condition here.
We can see the combo box getting filtered but not showing the name field of the Campaign set as a display field. Through developer tools also, we don’t see the name returned in this case. The same is the case if we use multiple If or Switch in the formula.
The solution is to filter on Campaigns data source directly, instead of the corresponding Choice field in the Lead.
Recently we were exploring the possibility of creating a marketing form submission record through flow/custom code. Here simply creating the marketing form submission record is not enough, for it to be processed by the platform, we need to call the bound action – msdyncrm_UpdateMarketingFormSubmission with Step = Retry. (And it’s all not an officially supported scenario, so be careful)
Below is how the flow looks like
First, we create a form submission record –
After creating the form submission record, we are creating and associating the marketing field submission records with the values that we want to pass for the form – email, first name, and last name in this case.
And then eventually calling the action –msdyncrm_UpdateMarketingFormSubmission to trigger the submission (resubmit) of the form submission record.
On running the flow, we can see the record created with the status as pending.
Within a few seconds, if the input is correct, we can see the status updated as success
and the corresponding contact/lead created or updated.
Recently while working on a custom page we had a requirement to show different screens on the app start based on a choice field in the record. (The custom page was being opened from a button/command on the form)
For the custom page’s App OnStart we were first removing the curly brackets from the recordID parameter passed to set the ContractId variable followed by setting ContractRecord variable using that GUID in the LookUp function.
Now based on Contract Type optionset field in the Contract record we wanted to show a different screen as the start screen. However, trying to use the Global Variable in the StartScreen function gave us the error – “Global Variables are not allowed in StartScreen”
The solution here was to use the Param recordId to get the record and set the start screen accordingly in the StartScreen instead of ContractRecord global variable.