{"id":1493,"date":"2022-05-10T14:20:59","date_gmt":"2022-05-10T14:20:59","guid":{"rendered":"https:\/\/morecpq.com\/?p=1493"},"modified":"2022-05-10T17:55:54","modified_gmt":"2022-05-10T17:55:54","slug":"custom-settings-field-metadata","status":"publish","type":"post","link":"https:\/\/morecpq.com\/index.php\/2022\/05\/10\/custom-settings-field-metadata\/","title":{"rendered":"Custom Settings – Field Metadata"},"content":{"rendered":"\n

What. in tarNATION. is THAT?! Hey I found a custom setting that is in CPQ but I have no idea what it does or how it fits into the CPQ system. Here’s an answer! Honestly not sure if this is 100% accurate but this is what I’ve learned so far.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

There\u2019s no docs that I\u2019ve ever seen but it has to do with the fields used in price rules. This is one of the tables that get set up when you run execute scripts. It\u2019s what the error means when\u00a0 you add a field (that doesn\u2019t exist) to a Price Rule: “No Metadata found for field <fieldname>.” It\u2019s basically a list of fields (and their objects) that are referenced in price rules. You don’t have access to the data for this. So opening up and managing the data in this Custom Setting doesn’t show you anything. This data is internally managed by CPQ.<\/p>\n\n\n\n

Also! Chris Hickman<\/a> notes: <\/p>\n\n\n\n

“Back in the pre-Lightning UX days, which were predominantly when “Salesforce CPQ” was still “SteelBrick” (or even “Quote Quickly” before that), the “New Quote” button on Opportunity “did” a lot more than the Lightning UX-equivalent does, in terms of pre-populating fields, even during new record creation prior to save. You could take this even further by adding records to the Field Metadata custom setting. There was extensive documentation for this in the old SteelBrick community which unfortunately did not survive the Salesforce acquisition.”<\/p>\n\n\n\n

Below is a complete set of documentation lifted from this article<\/a>. Keep in mind, this old feature of CPQ used “URL hacking” which only works in classic. It’s also not a best practice to use this type of “URL hacking” in general.<\/p>\n\n\n\n

A specific set of fields on Quote can be auto-populated<\/u><\/strong> from the associated Opportunity<\/strong> and Account<\/strong> at the time of creating a new Quote.<\/p>\n\n\n\n

If you do not do the necessary setup, sales reps would spend time re-entering Quote fields which were already filled in at the time of creating Opportunity and Account.<\/p>\n\n\n\n

\"New
New Quote Creation Page WITHOUT auto-populated fields<\/figcaption><\/figure>\n\n\n\n

Salesforce CPQ provides a Field Metadata<\/strong> custom setting where we can set up the fields that we want to be pre-filled with the corresponding values on Quote creation.<\/p>\n\n\n\n

\"AUTO-POPULATE
New Quote Creation Page WITH auto-populated fields<\/figcaption><\/figure>\n\n\n\n

Use Case<\/h2>\n\n\n\n

John Cook works as a CPQ Administrator at Universal Containers (UC). Usually, Sales reps at UC go through Account -> Opportunity -> Quote<\/strong> flow to create new Opportunities and Quotes.<\/p>\n\n\n\n

While creating a new Opportunity from an Account, lookup to that Account gets set on the Opportunity. While creating a new Quote from an Opportunity, lookup to that Opportunity gets set but, lookup to the Opportunity\u2019s Account DOESN\u2019T get set <\/strong>on the Quote. Reps have to explicitly select the corresponding Account in Account field on the Quote.<\/p>\n\n\n\n

Sales Reps expect that the system should be smart enough to automatically pre-populate the Account lookup on Quote with its Opportunity\u2019s Account.<\/p>\n\n\n\n

How to Setup?<\/strong><\/h2>\n\n\n\n
  1. Navigate to Setup | Develop | Custom Settings | Field Metadata<\/strong>. Click Manage<\/strong>\"FieldField Metadata<\/li>
  2. Click New<\/strong> on the Field Metadata page.<\/li>
  3. Enter the Name<\/strong>, Field Name and Object Name<\/strong> of the Field you want to auto-populate where