There Was a Problem Saving the Event Please Try Again 9001 Salesforce
Have y'all been using Salesforce Field Service Lightning? Perhaps you configured the product to fit in with your field service processes and now administer information technology for your company? Well if yous tin can relate to whatever of those I am pretty sure you will accept had some product hiccups along your FSL journeying.
Like most implementations, pre and postal service production stages have their challenges. The showtime, getting to know the product and then adapting it to your business organization needs. During this stage information technology is very easy to miss features that might take a big impact on the way FSL works for you. This is particularly true equally most config tin't be applied to alter sets; You really have to remember all config changes betwixt your testing surroundings and live. The second challenge is going live. Yous have gone alive with the product and your service resource are using the product. During this teething phase the chances of receiving FSL issues are relatively high.
Having experienced a number of problems myself, I can happily say, like many things with Salesforce, at that place is pretty much ever a solution.
Here are a few bumps I experienced and solutions I constitute along my FSL journey. Hopefully they tin can help you on yours.
Missing Resource
Trouble: When an appointments condition is set to a custom value e.g ''Travelling' – The resources is removed from the Service Appointment.
Solution: When creating a new status value you will need to specify their 'Category Status'. In this example more than probable the respective category will accept been 'None'. This will remove the resource and reset the service appointment. Merely changing the Category Status to 'In Progress', 'Schedule' etc will resolve the issue.
Unable to generate Service Report
Problem: This ane seems to be a popular one amid the FSL customs. Your field rep is out on a job when they report that they are unable to generate a Service Report from a piece of work order via the FSL app. This is a fundamental case of the forgotten manual config between orgs.
Solution: Make sure you have assigned a Service Report Template to all Piece of work Type records.
Absent Resources beingness booked for appointments
Problem: The calendar is scheduling appointments fifty-fifty if resources accept absences scheduled. If like me y'all implemented an approval process back in the twenty-four hour period that appeared to work correctly with FSL scheduling and then all of a sudden found out that it no longer worked. Nosotros can thank to a little Winter18 update called 'Approval Confirmation', for that.
Solution: Firstly add the 'Approved' field to the Resource Absence page layout. Then navigate to FSL Settings >Scheduling>General Logic> and enable 'Actuate Approval confirmation on resource absences'. Enabling this option will remove all absences from the Gantt nautical chart, this is to exist intended. Once this is enabled, you lot will then demand to retrospectively brand this checkbox true on all future absence approval records. This will then resubmit the record into approval where past the manager will need to re-approve for the absence to 1) reappear on the Gantt chart and 2) to exist taken into consideration when scheduling resources.
Data Integration Lag
Problem: You or some of your users may have reported an issue with the Data Integration Rule. Sometimes you may run into the condition 'Non Compared', this means that the address on the SA tape hasn't been compared with the available address records in the Data.com service. As a result this could affect scheduling every bit booking an appointment takes into consideration the accost on the SA. And while the upshot is commonly brusque lived and doesn't necessarily pose a dandy impact on Appointment booking, there are moments where this could exist an result.
Solution: Not much of a solution I'm afraid. If you demand to book an appointment as before long as the record is created, but see a status other than 'In Sync', expect a moment and click the update action. This does mean that you have to keep an eye on the Information Integration Rule Condition.
Future Appointments are being dispatched
Trouble: You lot arrive at work to observe that some of your Service Appointments scheduled in the next 24 hours accept been dispatched. This doesn't fit in with your manual mass dispatching which happens the night before the appointment scheduled appointment.
Solution: In that location is a little checkbox in the FSL settings called Machine Dispatch. If want your dispatchers to accept manual command on SA then deselect this choice. If not, information technology's a rather neat feature to accept enabled!
Problem: Do yous have bug where the next Service appointments are automatically being dispatched when a previous / current appointment has been completed /cancelled?
Solution: Again this is another ane of those pocket-sized checkbox features that can cause issue to your service appointments. Located in your FSL settings, search for Drip Feed and configure / disable this characteristic.
Remove Skills
Problem: If like me you were wondering if it is possible to delete skills – Unfortunately this is not possible, currently.
If you have anymore issues, delight leave a comment on this web log or take reward of the community, they actually are brilliant!
I'd like to say a massive thank you to all those in the Salesforce Partner Customs Grouping – Field Service Experts. You've made and go on to make the FSL journeying that much smoother.
See you before long
Jenny
Source: https://www.desynit.com/jennys-admin-tips/salesforce-field-service-lightning-issues-solutions/
Post a Comment for "There Was a Problem Saving the Event Please Try Again 9001 Salesforce"