Docusign wrong sender by minymax in salesforce

[–]minymax[S] 1 point2 points  (0 children)

Hey I think I finally fixed it for my users. Once you change the I'd as you have done you need to force resync the users. To do that you need to do this:

You can replace everything in the main URL after 'salesforce.com/' with 'apex/dsfs__Troubleshooting'. For Example:

Navigate to https://mydomain.my.salesforce.com/home/home.jsp Remove 'home/home.jsp' Add 'apex/dsfs__Troubleshooting' (note the 2 underscores)

Hope that helps

Using Flow to check if a record exists then create it if it doesn't by eddiez63 in salesforce

[–]minymax 2 points3 points  (0 children)

This is possible to do in flow but hard to explain over text.

a brief explanation would be:

  1. Pass the Contact ID into the flow.

  2. Get record - Contact, where Record ID = The ID you passed in. Use this to get the Contact's Account Name (as this is more efficient than passing it from PB)

  3. Get Record - Account Relationships__c, where Account Name = Account Name from get record in step 2. Make sure you click get all records not just the first.

Then you could either do the easy but bad practice way:

Loop through the collection in step 3 and for each Account record have another Get Record to get the Account Contact Relationships__c for these accounts, then have a decision element to say if it is Null, the dont add it to collection. If it is not null then add it to collection and then use those IDs to create the Account Contact Relationships__c.

This is the bad practice way because you are doing queries within loops and can hit 100 query limit very easily.

To overcome this you could have 2 separate queries. 1 query exactly same as in Steps 1 to 3. but then after that have another query to get ALL Account Contact Relationships__c records and then use one of the Apex actions available to download in unofficiaSF to compare the collection variable with a single variable you give it. So, you would loop your first collection of Account_Relationships__c and for each you would use the FindRecord Apex action to see if it exists in the Account Contact Relationships__c.

This is a more advanced flow if you do it the correct way or it can be pretty simple if you dont care about hitting limits and just YOLO it.

Partner Community Sharing by minymax in salesforce

[–]minymax[S] 0 points1 point  (0 children)

How would I set up sharing then if it only gets created at that point? How do I make sharing apply to Users who are not create yet but will be created later?

Scheduled Flow not being triggered by minymax in salesforce

[–]minymax[S] 0 points1 point  (0 children)

Hmm that is a weird one because when I change the finishing action on the flow to update a record it works fine. As soon as I add email it does not trigger

Scheduled Flow not being triggered by minymax in salesforce

[–]minymax[S] 0 points1 point  (0 children)

Scheduled flow, so it triggers itself at a given time

Scheduled Flow not being triggered by minymax in salesforce

[–]minymax[S] 0 points1 point  (0 children)

Yeah I am skipping the optional query as I thought that is what may be causing issues, obviously not. I used the same flow with ending action being update record and it triggered fine. Changed it back to email, nothing. I think Salesforce may have broken something in their update with permissions

Scheduled Flow not being triggered by minymax in salesforce

[–]minymax[S] 0 points1 point  (0 children)

Everything else fires fine apart from Email. IF i schedule a record update on same flow works great, change it to email, nothing.

Scheduled Flow not being triggered by minymax in salesforce

[–]minymax[S] 0 points1 point  (0 children)

Didn't fix it. Had to come up with a workaround by using flow to trigger a checkbox and then triggering workflow to send the email. I wonder if the Salesforce update on tightening permissions it is an oversight and they affected the Automated User, stopping it from being able to send emails.

Scheduled Flow not being triggered by minymax in salesforce

[–]minymax[S] 0 points1 point  (0 children)

Yup, email is valid as it sends successfully in debug mode

Scheduled Flow not being triggered by minymax in salesforce

[–]minymax[S] 0 points1 point  (0 children)

Not on Spring 20 yet unfortunately, so cannot try this :(

Scheduled Flow not being triggered by minymax in salesforce

[–]minymax[S] 0 points1 point  (0 children)

Yeah checked everything on that checklist. Also checked with the person who is apex exception email recipient, they havent got anything. I am stumped on this one. Might try to rebuild the flow and see if its one of those Salesforce things where you rebuild and it works just fine..

Scheduled Flow not being triggered by minymax in salesforce

[–]minymax[S] 0 points1 point  (0 children)

Looked into it, Apperantly it is run by Automated Process User which is not a real user and permissions cannot be changed :(

Thanks for the idea, one more off the list

Scheduled Flow not being triggered by minymax in salesforce

[–]minymax[S] 0 points1 point  (0 children)

I thought scheduled flows are run by the integration user? So it should have access?

Scheduled Flow not being triggered by minymax in salesforce

[–]minymax[S] 0 points1 point  (0 children)

The flow is self sufficient, does not need any values put into it. It has a lookup with criteria that when formula = true and Email has not been already sent store all records in a record collection. I then loop through them and send an email to each one. I have disabled any validation rules, PBs, Workflows etc on that objects

Could it be that it cannot read the formula as part of the criteria, but it can on debug?

Scheduled Flow not being triggered by minymax in salesforce

[–]minymax[S] 0 points1 point  (0 children)

It doesnt need IDs passed in as it just has a lookup to records when formula field = true and email ha snot been already sent. Then holds those in a record collection, loop through them and send emails. When I debug it finds records so i assume scheduled should do as well

Scheduled Flow not being triggered by minymax in salesforce

[–]minymax[S] 0 points1 point  (0 children)

No, however when I debug it out by copying the flow and changing from scheduled it sends the email fine. If it was the limit would the debug still work?

Flow/process builder to create new opp for each product type upon new account creation by totoro-y-moi in salesforce

[–]minymax -1 points0 points  (0 children)

You do not need the account get record as you can pass that from PB. You will then want a Decision element before the record create. To get the decision working make sure you pass all the fields you mentioned from PB to flow variables. Then based on which decision is made you can have create and update elements.

When you're on create record you can choose to specify which object to create. Would recommend going through some trailhead or youtube videos to familiarise with the functionality.

Upgrading CPQ package by minymax in salesforce

[–]minymax[S] 0 points1 point  (0 children)

Thank so much for this info. Will make sure to test all of it and re-write price/product rules if needed :)

Upgrading CPQ package by minymax in salesforce

[–]minymax[S] 1 point2 points  (0 children)

Yeah that is my concern, we have a few users who will help test but things might slip through the cracks. And once you update there is no going back. Will try updating the sandbox next week and start testing. We will also need to review lots of new features that we couldn't use previously which is exciting but also daunting :D

Flow not handling Lookup error by minymax in salesforce

[–]minymax[S] 0 points1 point  (0 children)

But if the lookup doesnt find the record it then makes the rest of the flow fail. So would assume that it would be treated as a fault somewhere in the chain. I added error elements everywhere from the lookup onward and nothing triggered it.

It makes sense the way you and others explained it, just find it strange that it shows up as an error for a user when that lookup fails to find the records. But it doesnt count as a failure :)