I logged in as her from my laptop and was unable to replicate the issue as everything worked fine for me. We did a screensharing session and I logged in as myself on her computer, but we still encountered the issue.
Any other .xls files are opening just fine for her in Excel. She mentioned she did a Windows update yesterday and that might have something to do with it. It's just curious that it's only happening with Salesforce reports.
Has anybody else encountered this issue? Do you think this is more of a laptop problem or a Salesforce problem?
Contacted Salesforce Support and this is the article they gave for a temp fix: support.microsoft.com/en-us/kb/2994633. They also said "R&D team has investigated this matter and logged a New Issue for it to be repaired. Unfortunately, I cannot provide a timeline as to when this repair will be implemented due to Safe Harbor constraints."
Can I customize fields in the "log a call" shortcut menu in the feed? (more details and screenshots attached)
I was able to do this when I go through the "normal" log a call workflow (seen below):
Is it possible to alter the modal that pops up in that shorcut for the feed?
*** in this example I'm testing up to a 5 Tier Account Hierarchy (Compiled size: 342 characters) ***
IF(NOT(ISBLANK(Parent.Parent.Parent.Parent.Parent.Name)), Parent.Parent.Parent.Parent.Parent.Name, IF(NOT(ISBLANK(Parent.Parent.Parent.Parent.Name)), Parent.Parent.Parent.Parent.Name, IF(NOT(ISBLANK(Parent.Parent.Parent.Name)), Parent.Parent.Parent.Name, IF(NOT(ISBLANK(Parent.Parent.Name)), Parent.Parent.Name, IF(NOT(ISBLANK(Parent.Name)),Parent.Name, Name)))))
HYPERLINK('/' + IF(NOT(ISBLANK(Parent.Parent.Parent.Parent.Parent.Name)), Parent.Parent.Parent.Parent.Parent.Id, IF(NOT(ISBLANK(Parent.Parent.Parent.Parent.Name)), Parent.Parent.Parent.Parent.Id, IF(NOT(ISBLANK(Parent.Parent.Parent.Name)), Parent.Parent.Parent.Id, IF(NOT(ISBLANK(Parent.Parent.Name)), Parent.Parent.Id, IF(NOT(ISBLANK(Parent.Name)),Parent.Id, Id))))), IF(NOT(ISBLANK(Parent.Parent.Parent.Parent.Parent.Name)), Parent.Parent.Parent.Parent.Parent.Name, IF(NOT(ISBLANK(Parent.Parent.Parent.Parent.Name)), Parent.Parent.Parent.Parent.Name, IF(NOT(ISBLANK(Parent.Parent.Parent.Name)), Parent.Parent.Parent.Name, IF(NOT(ISBLANK(Parent.Parent.Name)), Parent.Parent.Name, IF(NOT(ISBLANK(Parent.Name)),Parent.Name, Name))))))
It didn't always work so I logged a case with SF and they fixed it by ticking 'Recursion - Allow process to evaluate a record multiple times in a single transaction?'
Now, when I asked SF why that needed to be ticked (so I can understand when/if I need to tick it on future processes) the reply was:
'Process works if there are relevant changes in the record. Now since the Field was left blank and does not have any changes then the system thinks that no changes was made. This normally happens when using a blank value in any conditions or criteria.'
But I don't understand! Why should a process set to run on creation of a record NEED a field to be changed to fit the criteria..? Why can't it just recognise that the criteria is met on the creation?
First test: impact of stopping the clock on the "Elapsed Time"
Target Date 25/02/2015 09:44
Stopped Since: 25/02/2015 09:35
Restarted at: 25/02/2015 09:47
Completed milestone at: 25/02/2015 09:47
Elapsed time after close: 13 mins
Violation NOT CHECKED! (although the elapsed time is greater than the target response time...) Target Date 25/02/2015 09:56 (moved by the time process was stopped)
so, the clock being stopped or not, does not influence the elapsed time while it should... Also, as long as the milestone is not yet completed, you have the "time remaining" which IS being influenced by the entitlement being stopped or not
Second test (as a sanity check... you would start doubting everything): impact of the business hours on the "Elapsed Time"
Case opened outside of business hours
business hours of day of testing: 10:00 to 10:05 AM
Start Date 25/02/2015 09:54 AM
Target Date 26/02/2015 00:55 AM
Target Response (Mins) 60
Completion milestone at: 25/02/2015 10:06
Elapsed time: 5 mins
so here, the business hours DO have impact on the elapsed time
could someone confirm this buggy behavior please and let me know if there are workarounds?
Sometimes things come up in software in general, where if something works differently than you'd expect, it might still be working as designed, which means there is no bug. Your opinion may be that the design is flawed, but first try to understand why it was designed a certain way to determine if the functionality meets your use cases.
So with all that said, what exactly are you wanting it to do?
It looks like the actual elapsed time was only a minute or so without being stopped, which explains why it didn't throw a violation. Target Response and Time Remaining should change based on starting/stopping, but Elapsed time shows total, less business hours.
If you want a field that calculates alpsed time, less stopped time, you have all the date fields, so try creating a formula which calculates your version of elapsed time.
Since Process scheduled actions don't appear in the time-based queue I can't find the answer through trial and error.
I know when a workflow rule's criteria changes that sets the time-based action on queue the time-based action is removed from the queue. Is this the same with Process Builder and scheduled actions? If a scheduled action is trigger since the criteria on the process is met will that scheduled action be removed if the criteria changes before it fires?
Thank you Douglass Yeager!
Here is my answer:
"For processes that are set to run when a record is created or edited, scheduled actions remain in the queue only as long as the criteria for those actions are still valid. If a record no longer matches the criteria, Salesforce removes the scheduled actions for that record from the queue."