Print this page

Retiring the Legacy HashtagDefinition Object - FAQs

Knowledge Article Number 000221237
Description We have started the process to retire and end support for the legacy HashtagDefinition object, and we will do that in two phases. In February 2016*, we will disable API access to legacy HashtagDefinition object for reporting, and in June 2016**, we will complete retirement of the object. We recommend that you redirect all queries and reports using the legacy HashtagDefinition object to use the Topic object. 
 

What is changing and when?

We will retire the HashtagDefinition object, a legacy object for reporting on hashtag usage in Chatter posts that has been replaced by Topic reporting. The retirement will take place in the following phases:

  1. With the Spring '16 release*, we will disable API access to legacy HashtagDefinition object for reporting. This means any integrations relying on API queries to this object will stop working. However, you will still be able to run reports through Report Builder in the User Interface (UI). If there are any issues, refer to the “Retiring the Legacy HashtagDefinition Object” article.

  2. With the Summer '16 release**, we will complete retirement of the legacy HashtagDefinition object. This means you will no longer be able to run reports in Report Builder that include the legacy HashtagDefinition object.

 

*Currently targeted for February 2016; date subject to change

**Currently targeted for June 2016; date subject to change

 

How will this affect my organization?

If you would like to run reports on hashtag usage on Chatter posts, you can use the Topic Assignments and Topic objects. Re-creating usage reports with the Topic object allows you to include more information than the legacy HashtagDefinition object, such as Created Date, Description, Name, and # Talking About.

 

What do you recommend?

We understand that this retirement may cause disruption for some customers using the legacy HashtagDefinition object, and we are here to help. When we introduced Topics in Summer 2013, all data was migrated from hashtags to Topics. We recommend that you redirect all queries and reports using the legacy HashtagDefinition object to use the Topic object. Hashtags can still be utilized in posts and comments and will continue to create corresponding topics.

 

For additional resources about using Topics, check out the following:

 

Why are you retiring this functionality?

We’re retiring the legacy HashtagDefinition object to focus our innovation efforts on features such as Topics, an enhanced feature that provides additional value.

 

For an overview of our philosophy on retiring functionality, please click here.

 

How can I get more information?

For additional questions, you can contact Customer Support by opening a case via the Help & Training portal.

____________________________

Frequently Asked Questions

  1. What exactly will happen after the retirement date passes?

  1. We will retire the legacy HashtagDefinition object in two phases:

    1. With the Spring '16 release*, we will disable API access to the legacy HashtagDefinition object. This means any integrations relying on API queries to this object will stop working. However, you will still be able to measure usage by creating reports through Report Builder in the User Interface (UI). If there are any issues, contact Customer Support by opening a case via the Help & Training portal.

    2. With the Summer '16 release**, we will complete retirement of the legacy HashtagDefinition object. This means you will no longer be able to run reports in Report Builder that include the legacy HashtagDefinition object.

 

*Currently targeted for February 2016; date subject to change

**Currently targeted for June 2016; date subject to change

 
  1. What is the recommendation?

  1. If you would like to measure usage, you can use the Topic Assignment and the Topic object to create a new custom report type.

  1. You can still create hashtags in your posts and comments. When we introduced Topics in Summer 2013, all data was migrated from hashtags to Topics. Those hashtags will continue to create corresponding topics, which are reportable with the Topic object. Additional information can be obtained with the Topic object, such as Created Date, Description, Name, and Talking About (number of people talking about the topic).

  2. If you would like to create a report that shows how often a topic is mentioned (count), you will need to create a summary report.

 
  1. What will happen if I do not take the recommended action?

  1. If you continue running reports on the legacy HashtagDefinition object, the report will not return information. Instead, you will see an error message stating “Insufficient Privileges.”

 
  1. What are Topics?

  1. Topics are words or phrases that you can associate with Chatter posts and most Salesforce records to describe and organize your data in a personalized way.

  2. To learn more about using Topics, refer to the “Adding Topics to Posts” Knowledge article.

 
  1. How do I use the Topic Assignment object for reporting?

  1. Reporting on assignments of a topic to posts and records can be done using the Topic Assignment object in Custom Report Types (CRT). You can report on the types of records topics are assigned to, as well information about the topics themselves.

  2. In addition to reporting, you can use SOQL to obtain information from the Topic Assignment object for other use cases. Please refer to the TopicAssignment section of the SOAP API Developer's Guide.

 
  1. What will happen to my data?

  1. When we introduced Topics in Summer 2013, all data was migrated from hashtags to Topics. Your data will not be deleted, but the legacy HashtagDefinition object will not be accessible.

 
  1. Where can I find additional information?

  1. For additional questions, you can contact Customer Support by opening a case via the Help & Training portal.




promote demote