Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics 365 | Integration, Dataverse...
Suggested answer

BPF not showing for cases created by a flow

Posted on by 10

BPF isn't showing up at all for cases created by a flow. 

This flow creates cases and related accounts and contacts from a Dataverse entity that (in a separate flow) is pulling data from a constantly updated .xlsx stored in SharePoint.

The trigger for this flow that writes values from one Dataverse entity to these three other Dataverse entities is when a row is created in the Dataverse table. The actions are create new row in Case, create new row in Account, and create new row in Contact.

So the BPF enabled for this app is not showing up (it literally just isn't there) for these cases created with the flow, nor is the javascript for the page that controls tab visibility working.

However, the BPF and JS show up and work when a case is created manually.

(license = Dynamics for Customer Service)

  • Suggested answer
    Wahaj Rashid Profile Picture
    Wahaj Rashid 11,319 on at
    RE: BPF not showing for cases created by a flow

    Hi,

    Thank you for your query.

    Here is the logic how BPF is applied while creating a record programmatically (or flow).

    Work with business process flows using code (Developer Guide for Dynamics 365 Customer Engagement) | Microsoft Docs

    You can also override this behavior by setting ProcessId field (you can do this in the flow).

    If it still doesn't work, there could be multiple reasons, I am listing few for your troubleshooting:

    • The user (used in flow), have privileges on Business Process flow entity?

    Work with business process flows using code (Developer Guide for Dynamics 365 Customer Engagement) | Microsoft Docs

    • For the tabs (JavaScript) issue, you need to review your code and understand which fields switch the tabs. It is possible, while creating these records programmatically, you are not setting these values. For example, a Business Type is set using a Business Rule, which is scoped to run on a form. This means, when you create the record programmatically, this rule is not executed (unless scope is set to Entity).

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,214 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans