Frequently Asked Questions

How does it work?

The App works as follows (assuming that we are referring to the Lead object):

1. First it checks the Lead address fields and if there are valid values, it uses these values to find the time zone information.
2. If step (1) fails due to incorrect values in the fields, it will then attempt to use the Lead phone number field to find the time zone information.
3. If step (2) fails, it will then check if the country value of this lead record has multiple time zones, and if the answer is yes, it will get the time zone defined in the Default Timezones setting.
4. If all the above attempts fail, the App shows the value Unknown for the Local Time field.

What address fields are used by the App?

For countries with multiple time zones, the App’s lookup logic requires both country and state values (Example: USA, NY). For countries with a single time zone, just the country value is adequate (Example: Germany). The App does not use the street address or city field values.
 

How does the Default Country option work?

This setting is useful when you have records that do not have both the country and phone fields populated. In such cases, the App uses this setting to find the time zone information.

In the following example, both the country and phone fields are empty. The App therefore used USA as the country (assuming that the Default Country option is set to USA) and returns the Pacific Time Zone information as the state field is CA (California).

How does the Default Timezones option work?

For countries with multiple time zones, the App’s lookup logic needs both country and state address field values. If you have some records where only country field is populated but not the state field, this lookup fails and the App shows a value “Unknown” in the Local Time field for those records. If you would rather prefer to have a default time zone used in these cases, you can define them here. Otherwise, you can leave these settings undefined.

Example: You have a lead record where the Country field = USA but the State field is blank. The Local Time field value is thus shown as Unknown. If you define the default time zone for USA as America/New_York, then this lead record will show the Local Time fields with US Eastern time zone related values.
 

Can I define multiple address/phone fields for the time zone lookups?

Yes, and you can do it from the Local Time Config tab, as shown in the following screenshot.

When there are multiple entries for a given object, the time zone lookup logic processes one entry at a time. In the above example:

• The App does the lookup based on the information from the first entry. If the lookup succeeds with valid time zone information, the App does not process any other following entries.
• If the lookup based on the first entry fails, then the App proceeds forward and does a lookup based on the information from the second entry.
• If all the entries are processed and time zone lookup fails, then the App shows the value Unknown in the Local Time field.

 

Does the App show the correct time zone information for US states with multiple time zones?

Yes. The US states such as Texas, Florida, Kansas etc. have multiple time zones within the state. The App gives you the correct time zone if you also provide the Zip/Postal Code value. If this value is empty, then the App will show the time zone which is most widely used in the state.
 

Time zone Without Postal Code:

Time zone With Postal Code:

Can the App do the time zone lookups based only on postal codes?

No. Currently due to space limitations for managed packages in Salesforce, its support for postal codes is limited.
Postal codes are only supported for states in the US and Canada which have multiple time zones. Example: Texas, Florida. In addition, we only store those postal codes where the time zone is different from the most widely used time zone in the state.
We recommend that you provide both state and postal code values in your records.

• If the postal code is empty, then the App will show the time zone which is most widely used in the state.
• If the postal code is not empty, then the App will provide the time zone specific for that postal code, if an entry for it exists in the App’s database.
• Please refer to the screenshots in the FAQ article above: Does the App show the correct time zone information for US states with multiple time zones? to understand how the App currently works.

Does the App support time zones on Salesforce custom objects?

Yes. Please check this blog post on how to get time zone information on custom objects where you want to store this information in custom fields.
Another option is to use the Local Time Lightning Component. Please check this blog post on how to configure it to work with a custom object.
 

Does the App support API calls from Salesforce Apex code?

Yes. Please check this blog post on how to get time zone information from apex code.
 

Can I delete the scheduled job LocalTimeSchedulerDaily?

No. This scheduled job checks for DST changes daily and thus we advise you not to delete it. In case you deleted it by mistake, please go to Local Time Config tab and then click the Save button. This will schedule this job again.
 

How to resolve error email Developer script exception: ‘tz.LocalTimeScheduler’ : Inactive User?

This error occurs when the LocalTimeSchedulerDaily is submitted by a user who is no longer active in your Salesforce org. Thus the scheduled job will not run and the time zones may not reflect DST changes. Login to Salesforce with a user that has the system administrator profile and do the following to fix this issue:
1. Go to Setup -> Administration Setup -> Monitoring -> Scheduled jobs and delete the job titled LocalTimeSchedulerDaily.
2. Click on the Local Time Config tab and then click the Save button. This will schedule the batch job with an active userid.
 

Why are the time zones are off by an hour?

The LocalTimeSchedulerDaily scheduled job, which checks for DST changes daily is most likely deleted. Please go to Local Time Config tab and click the Save button. This will schedule this job again and the time zones issue will be resolved.
 

Why are the time zones are off by an hour in the sandbox org but not in the production org?

This issue usually arises when you refreshed a sandbox org from the production org. Salesforce cannot automatically start the LocalTimeSchedulerDaily scheduled job in these cases. Please go to Local Time Config tab in the sandbox org and click the Save button. This will schedule the job and the time zones issue will be resolved.
 

How do I resolve System.LimitException: Apex CPU time limit exceeded errors?

This error usually occurs when a transaction hits the 10 sec CPU usage governor limit of Salesforce.

• Please check the automations (process builders, flows, triggers etc.) that you have implemented on the object and investigate which one of them is consuming the CPU time and see what you can do to improve their performance.
• If you are not using the Local Time App for any of these objects (Accounts, Leads, Contacts, Tasks, and Events), you can turn off the appropriate triggers from the Local Time Config tab -> Settings tab.
• If you indeed need to use the Local Time App for any of these objects, then ensure that you have also turned on the After Trigger for the relevant objects. Doing so will ensure that the App will process these records asynchronously when the number of records in the trigger exceeds the limit specified in the Record Limit setting. This is typically useful when the records are being created/updated via bulk operations.
  

 

How do I purchase the App?

Please send us an email at info@success-software.biz and we will send you an invoice. After the payment is made, we will convert your free trial of the App to an active site license. Please note that the free trial is valid for 30 days and is limited to max. 10 users only.
 

Do you offer discounts for non-profit organizations?

Yes, we offer 50% discount off the list price for the App.
 

What address and phone formats does it support?

Please refer to the following appendices to understand the proper formats:
Appendix A – Supported Country List
Appendix B – Supported Phone Formats
 

How can I visually indicate if it is a good time to call a subject?

You can create a formula field and use images to indicate if the local time of a record falls within the local office hours or not. This formula field can be added to page layouts and list views to help prioritize calling your subjects.

Following is a sample formula field (return type Text) on the Lead object. The formula shows a yellow flag if the local time is earlier than 9 am, a green flag if the local time is between 9 am and 5 pm, and a red flag if the local time is later than 5 pm. You can create similar fields on other standard objects supported by the Local Time App.

IF(ISBLANK(tz__UTF_Offset_F__c),
"Unknown",

IF(VALUE(MID( TEXT( NOW()+ tz__UTF_Offset_F__c /24 ), 12, 2 )) < 9,
 IMAGE("/img/samples/flag_yellow.gif", "Yellow", 18, 18),

IF(VALUE(MID( TEXT( NOW()+ tz__UTF_Offset_F__c /24 ), 12, 2 )) > 17,
 IMAGE("/img/samples/flag_red.gif", "Red", 18, 18),
 IMAGE("/img/samples/flag_green.gif", "Green", 18, 18)
)
)

)

 

How do I update old records to show local time?

By default, the App shows local time for new records created after the App is installed or when you manually update records. However this can be an issue if you have to manually update each old record. To mass update old records, utilize the following steps:

1. Go to Local Time Config tab.
2. Select the Mass Update subtab.



3. Select the relevant object. If needed, tweak the WHERE clause to narrow the query down to the records that you would like to be updated.
4. Click the Update button so start the mass update batch job.

 

How do I show time zone information on Case or Opportunity?

The Case object has a lookup reference to the Account and Contact objects. Similarly the Opportunity object has a lookup reference to the Account object. Thus, depending on your use case, you can create a formula field in the Case / Opportunity object to get the time zone information from the appropriate Local Time App related fields in the Account / Contact object.
 

The App works for me (SysAdmin) but not for other users

During the installation process, it is important that you have selected the option Grant access to all users. If you have not done so, then you have to manually give the users or the profiles access to the App, Apex classes, visualforce pages, and custom fields.

How do I customize the App?

From Salesforce Lightning Experience App Launcher, select the Local Time App. Click the Local Time Config tab to customize the App and then click on the Save button to apply the new settings.
 

How can I use Local Time in reports?

The Local Time and UTC Offset custom fields can be used in list views and reports.

The UTC Offset custom field is automatically updated whenever you create or update a record. The Local Time custom field is a formula which utilizes the UTC Offset custom field in its calculation. These fields can be used in a couple of ways:

1. In reports so that you can sort the reports based on the timezone (the UTC Offset field).

2. In list views so that you can sort and prioritize your calling lists accordingly.

How do I uninstall the App?

The App can be uninstalled with the following steps:

1. Remove all references to the Local Time Gadget, Local Time Button, and Local Time Lightning Components and Actions in all the page layouts where you have initially added them.
2. Go to Setup -> Apps -> Installed Packages and click on the Uninstall link located next to the Local Time App.

 

How do I grant login access to a Success Software supporter?

You can grant login access to your Salesforce org as follows:
Click on Setup | My Personal Information | Grant Login Access -> Select a couple of days for Success Software
or
Click on Your Name | My Settings | Personal | Grant Account Login Access -> Select a couple of days for Success Software