Contents
How to create an object in a flow?
I have a Flow, triggered from D365, creates a ‘connection’ between two entities. To do this, I have a variable opportunityPartner, type: object, initial value: null (). I set the variable in my Flow:
What’s the best way to name a flow?
There’s no right or wrong way to do this; just keep it consistent within the flow. One popular naming convention is called Camel Case. Check out this nifty Wiki article from the Salesforce Exchange Discord Server on suggestions for flow naming.
How to get the whatid of an object?
You can do that by specifying that the WhatId is between the min and max Id values for that given object like so: Using this approach, all the heavy lifting is done at the database level and one doesn’t have to waste Apex CPU time doing the filtering. Unfortunately, the “like” operator isn’t supported on Id fields.
How to get object type of whatid task / event fields?
Yes that would also work. what tech note are you referring to? the URL in the previous post is dead… please let us know!!! The best way is to query for the type when you query for the Id, e.g. oh thanks, i ended up doing what another user posted and it worked!
Can a flow have more than 250 actions?
But, because of the restriction (A flow can have only 250 actions), I cannot exactly convert the same. As a workaround, Microsoft itself, suggesting to go with the Nested Flows. i.e., Consuming a flow within a Flow. Hence, the flows which goes beyond 250 actions can be splitted to separate flows and can be consumed as methods.
How to select input pins in object flow?
For example, a list of available options to select input Pins opens when drawing Object Flow to the Action that has more than one hidden Input Pin. From an Object Flow shortcut menu on a diagram pane, select Refactor and then select Split Object Flow .
How to solve Microsoft Flow combining multiple values?
The suggested solution at the bottom of page 2 of this post was the starting point of figuring this out: https://powerusers.microsoft.com/t5/General-Flow-Discussion/SharePoint-list-submission-notification-… . This solution did send out a single email but the sting produced was a series of odata strings.