< Return to the Knowledge Base Home Page

Contents

...

After clicking Start in the Stopwatch, the newly started Time Tracking Summary doesn’t appear in the Stopwatch. Other active Time Tracking Summaries also don’t appear in the Stopwatch.

The issue occurs when a custom field is created on the Time Tracking Summary object with the same API Name as a field in the Time Tracking managed package.

A workaround The resolution is to change the API Name of the field to a name that doesn’t match a field in the managed package.

The issue will be resolved in a future Time Tracking App release.

Replication Steps

In the Stopwatch, do the following:

...

The issue occurs when a custom field is created on the Time Tracking Summary object with the same API Name as a field in the Time Tracking managed package. For example, if a custom field with the API Name Account__c is created, the issue occurs because there is a field in the managed package named TTracking__Account__c. Because the API Names of the two fields match when ignoring the TTracking namespace, the issue occurs.

...

Resolution

The issue can be avoided resolved by making sure that no custom fields on the Time Tracking Summary object have the same API Name as fields in the Time Tracking managed package. For example, if there is a custom field with the API Name Account__c, change the API Name of the Account__c field to a name that doesn’t match the API Name of any field in the managed package, such as Account2__c.

Identify the field that is causing the issue

To identify the field that is causing the issue, do the following:You can identify the problem field in the user interface, as well as in the browser’s DevTools.

Identify the field in the user interface

When the Stopwatch loads, if the issue is encountered, the field name is displayed in an error message at the top of the page.

...

Identify the field using the browser’s DevTools

1. In the Stopwatch, do the following:

   1. Populate the Account field.

   2. If desired, populate the second Lookup field.

   3. Click Start.

2. Open your browser’s DevTools.

3. In the Console tab in DevTools, find the Server Error error message, which specifies the field that is causing the issue. Look for “duplicate field selected”.
   

   

Resolution

...

Future State

To be able to have custom fields with the same names as fields in the Time Tracking package, vote for this Idea on the Salesforce IdeaExchange.