Here I am facing an issue with with my Flow and Process Builder.
Basically, I am trying to create a Flow which Mark a Note as Recent Note when a "Note is Created or Edited" and Uncheck the Previous Note.
For that I created a Flow and Then Process builder (Start the Process when a Record is created or Edited)
Here I am getting an Error as below:
Error element Update_Other_Notes (FlowRecordUpdate).
The flow tried to update these records: null. This error occurred: DUPLICATE_VALUE: Maximum number of duplicate updates in one batch (12 allowed). Attempt to update Id more than once in this Api call:
On the Other hand, I am using similar Flow and Process Builder to update my Recent Case when a Case is created and Uncheck the Old one and that is working perfectly fine.
The Only difference is that "On my Case object, I used start the Process only when a record is created". If I use the same process criteria in Notes and thats too working.
The Only thing is I am getting above error when I use criteria that Start the Process When record is created or Edited.
Any Help will be highly regarded.
I think you're running into an infinite loop, where the flow updating the notes triggers the process again, which in turn triggers the flow, which in turn triggers the process infinitely.
You'll need to make sure your flow is only executed when your note meets specific changes, like only when it is being created.
I want to learn Visualforce and Apex coding,Could anyone suggest me good workbook or related books(Prefer PDF) to learn those things.......
Thanks & Best Regards
I will suggest you to Learn Through Trailhead Initially,
After Doing This Trailheads, you can Google it and you will find Lot and Good Blogs by MVPS and Developers,
Check This Links,
Apex Tutorial------>https://www.tutorialspoint.com/apex/ (https://www.tutorialspoint.com/apex/)
I hope this Link will help you,If any Please let me know
All the Best For your Future :)
I want to know what does property 'enableLicensing' do for the object I am unable to find it on release notes and other online communities .
There doesn't seem to be any documentation about what EnableLicensing actually does, which means it's probably not meant for us to tinker with - or not a fully released feature yet. With that being said, I'm going to go out on a limb and say it could be something to do with AppExchange licensing management, which is a mechanism that allows ISVs to decide which features are accessible to clients depending on what tier of product they've purchased. It could be that this allows LMA to work on the object level -- but it's just a guess.
"Import and Export with Data Management Tools"
One of the requirement was to download the file then do same changes and save it agailn as CSV file. I followed all the steps and Import was successful. But when I verify the Challenge I got the following error
Challenge Not yet complete... here's what's wrong:
The 'Lead' records from the CSV were not found. Please check the instructions.
I dnt understand why I am getting this error. I did this project in a trailhead playground.
I had the same problem and it took some hours to find out the solution.
You could check your organization's default locale setting in"Company Information"
The default locale setting decides the way your lead's name is displayed within the system.
Suppose your lead's name is Cate Blanchett (First name: Cate / Last name: Blanchett)
and if your company's default locale is set to some non-english speaking countries like South Korea or China,
her name will be displayed as Blanchett Cate.
In this case, the Salesforce system cannot recognize her as the same person...
So, you could simply change your company's default locale setting to English (USA) or something.
Hope this works for you!
In Salesforce you have to open the email that added to Salesforce and under Attachment Related list you can find the attachment of the emaill See the screen shot:
If you don't have Attachment related list in email, you can edit the Task Page Layout and add the Attachment related list.
I'm trying to figure out why my validation rule isn't working. The rule is to require a complete billing address on the Account record before moving an Opportunity to Ready for Invoicing stage when the country on the Account is not United Sates. There is a field on the Opp called "Account Country" that is populated with the Account's country. (Alternatively, would be great to be able to say "require these fields if the country is United States, and if the country is not united states, require all fields but the state field).
My validation rule currently looks like this, but I can't move the Opp to Ready for Invoicing even when the country is not United States:
ISPICKVAL(StageName, "Ready for Invoicing"),
RecordType.Name = "Opportunity Record Type - B2B Sales",
Account_Country__c <> "United States",
Non United States:
AND( ISPICKVAL(StageName, "Ready for Invoicing"), RecordType.Name = "Opportunity Record Type - B2B Sales", Account.BillingCountry <> "United States", OR( ISBLANK(Account.BillingStreet), ISBLANK(Account.BillingCity), ISBLANK(Account.BillingPostalCode), ISBLANK(Account.BillingCountry), ISBLANK(Account.Company_Legal_Name__c) ))
AND( ISPICKVAL(StageName, "Ready for Invoicing"), RecordType.Name = "Opportunity Record Type - B2B Sales", Account.BillingCountry = "United States", OR( ISBLANK(Account.BillingStreet), ISBLANK(Account.BillingCity), ISBLANK(Account.BillingPostalCode), ISBLANK(Account.BillingState), ISBLANK(Account.BillingCountry), ISBLANK(Account.Company_Legal_Name__c) ))And also there is no need to use "Account_Country__c" field as it is the reference to Account.BillingCountry field.
SharePoint Online - Can't access external source - External data source is unavailable because of an error
I've followed all of the documentation (haven't found any more recent than 2017) to no avail. I thought I would repost the question to see if there are any definitive solutions. Here's what I'm getting.
My question, don't they essentially do the same thing? Is it better practice to have the case assignment rule activated and in place and deactivate my workflow rules? or should I leave it be and delete the assignment rule I don't have active?
I will be adding more departments to this process and something tells me that I shouldn't just make tons of workflow rules over and over
Thank you in advance for your guidance!
Let's say you only need initial 'assignment', then using Assignment Rules makes a lot of sense. However, if you also want to 'assignments' during a Case lifecycle, you will have to use Workflow Rules (which means duplicating the rules).
It really depends if you want to use Assigment. The pattern I usually suggest is to use Assignment Rules to 'filter out' the garbage records (send them to a Queue, for example), then use Workflow Rules for your actual 'real' assignments. You only have 1 set of rules to maintain, and you can create a custom view on the Workflow Screen to show you only your 'Assignment' rules if you use a naming convention.
All your assignment rules will be in one place, managable all in one screen (with workflows & field updated you will end up creating multiples and cannot view them all the rules in one screen.)
"Assigment rules they dictate which Salesforce user becomes the owner of a record, based on some criteria.
Workflow rules they make things happen like creating tasks, sending emails or updating fields based on things that happen to records that already exist in the system."
It is indeed better to choose one. Personally I use more assigment rules for leads and cases. Once the data has moved further in the system, workflow rules and process builder take over.