web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Conditional step in Web Forms for D365 Portal

(0) ShareShare
ReportReport
Posted on by

I am running into a peculiar issue on Conditional step for D365 Portal.
The scenario is below.
I have 3 tabs, for each tab i have created a step in the Web Form.
Tab 1 has a filed which is of type two options [Yes or No].
If the user chooses tab 1 value as Yes, my second step should show fields in Tab 2.
if the user chooses tab 2 value as No, fields on Tab 3 should be displayed.
I have a conditional step which checks if the "field = true" and next step as Step 2. -> This works.
However if I chose No as the value, it throws an error " We are sorry ........... "

This conditional branching does not have a placeholder to handle the else condition.

What should be my next direction ?
Any help is much appreciated.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    RaviKashyap Profile Picture
    55,410 Moderator on at

    Hi Arun,

    The Next Step field will load the step if the condition is true; if the condition is false then it will load the step from the field 'Next Step If Condition Fails'.

    Portal-condtion.png

    Hope this helps.

  • Verified answer
    Community Member Profile Picture
    on at

    I was able to get this working, and i have written a small document on how i achieved this.

    Please refer the link below,

    technology-codesnippet.blogspot.in/.../conditional-step-type-for-web-form-on.html

  • RaviKashyap Profile Picture
    55,410 Moderator on at

    Hi Arun,

    If I am not wrong this is what was suggested above. Could you please share whats the difference in the above suggestion and your findings? It may help some one looking for the solution on this.

  • Community Member Profile Picture
    on at

    Hi Ravi,

    Thanks for looking into the document.

    Like I mentioned my case was peculiar, and hope you have seen the workflow in the document, Say Step 2 condition is false, it has to go to Step 4 and not Step 3, the Next step and Condition failed step are marked as you mentioned as well, but didn't work the way i wanted this to work.

    The differences are,

    a. The Entity source step on the next step was to be changed to Condition than the Load tab.

    b. The Metadata had to be correctly associated so that system knows there are other tabs to be overlooked.

    If the workflow was linear, what you suggested would have worked perfect.

  • RaviKashyap Profile Picture
    55,410 Moderator on at

    Thanks Arun.

    Hopefully this will help other. Thanks for sharing

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans