Field Indexing

Overview


The default duration defined for the “last sender” functionality (i.e. available for SMS Magic Interact ver. 1.48 and below) is 7 days. In other words, it checks the SMS History records for the past 7 days and if the phone number matches with the incoming SMS record, then, pulls in the SMS History owner.

We can increase the cut-off date from 7 to 30 using the following procedure to Index Fields:

  1. Under Salesforce Setup, click Custom Settings.
  2. Under Duration To View History For Incoming click Manage and then click New.
  3. Type a new name and extend the value for the field noOfDaysForCutOffDate to 30.

However, if the customer sends out a lot of text (more than 10,000), then, the query which we run to check the SMS history record will not work correctly.
In such cases, we need to raise a request with SF Support Team to get the field indexed along with the relevant Query.


  1. Ask the customer to provide subscribers access to Salesforce support.
  2. Get the org ID.
  3. Go to partners.salesforce.com to create a partner case.
  4. Log in using CS LMA login.
  5. Under the Support Section, create a New Case.
  6. Select the category as Salesforce Functionality.
  7. Create a Case.
  8. Add the severity level.
  9. Provide the following details:
    • ORG ID
    • Indicate if the access is provided
    • The need for this functionality.
  10. Provide the Query and field to be indexed based on the SMS-Magic Package version the customer is using (Refer to the section on Queries to view the fields to be indexed based on the package version).
  11. Also add the binding Values (ie. variables which are used after the Where clause of the query) for the query in the ticket.
  12. Provide the following details on the case:
    • What percentage (%) of your users are affected?
      — Add the percentage (%) of users for the Account who are using the app.
    • Does this affect data integrity?
      — Yes. Incoming messages are not associated with Outgoing messages.
    • Do you have a viable workaround?
      — No.
    • Does this affect critical application functionality?
      — Yes. We wish to index phone and sender id field of our custom object. When the customer receives SMS, we will query this custom object and if the records are huge (more than 10,000) then the query will timeout and the incoming SMS will not get attached to outgoing SMS which will impact our business.
    • What business functionality are you unable to perform?
      — To Receive incoming SMS and notify the correct user

Was This Article Helpful?

ATTENTION!!!! - Urgent Action Required

There have been new changes by the TCR that require companies sending application-to-person (A2P) SMS or Text messages within the United States to register their Brand and 10-digit long code (10DLC) numbers they are using.

The goal is to build trust within the system while delivering high customer engagement. SMS Text Messages will start failing if you don't comply with these regulations.

SMS Magic team wants to help you complete this process so you can continue serving your customers.

Please click on the below link to complete the form, and our team will start the registration process.