Creating an App from the Financial Analytics Template

The configuration wizard for Financial Analytics enables you to generate an app containing datasets, dashboards, and lenses by providing answers to questions about the values you need to create your dashboards.

To use the configuration wizard:

  1. Click Create in Analytics Studio.
  2. Click App.
  3. Select the Financial Analytics template, then click Continue. Provide your answers to each question. See below for a list of the questions included in the configuration wizard.
  4. Name your app then click Create.

Your app is now available on the Apps page. Lenses can be retrieved in XL Plus.

By default, when you generate an app the sharing settings are set to private. To give access to other users, click . This opens the app's Give Access tab. For more information about sharing Analytics apps, see the Salesforce Help.

Note:

If you make any errors while answering the questions about your app, you are notified at the end of the wizard. Click Continue to return to the wizard then use the Back button to find the relevant page and make your correction. After correcting any errors, click Continue to generate the app.

Ensure that:

  • There are cash matching history records in your org. For more information, see About Cash Matching.
  • The Incremental Sync checkbox is deselected on the CashMatchingHistory_READ node of the recipe.

To create your app, you are required to provide responses to the following questions in the configuration wizard. Questions marked with an asterisk (*) are mandatory.

Note: Questions 1 relate to all dashboards, question 2 relates exclusively to the Financial Statements dashboards, and questions 4, 6, 7, and 8 are not supported in sandbox environments.
Financial Analytics Configuration Wizard Questions

Question

Description
1. If the name of your general ledger account starts with a code, how many characters does the code have?* Specify the number of characters in the code. For example, if the general ledger account is called 4000-Sales, you would enter 5 as the number of characters in the code (4000-). If the general ledger account does not start with a code, enter 0 (mandatory response).
2. Which company is your default company?* Select your default Accounting company.
3a. For the General Ledger Type field, which value is your equivalent to Profit and Loss?* Select the value that represents Profit and Loss within your business.
3b. For the General Ledger Type field, which value is your equivalent to Balance Sheet?* Select the value that represents Balance Sheet within your business.
3c. For the General Ledger Type field, which value is your equivalent to Shareholders Equity?* Select the value that represents Shareholders Equity within your business.
3d. Which additional General Ledger Account Type values do you need to create your financial statements? Select any additional values you didn't already select in questions 3a to 3c that you need for your financial statements.
4a. Which additional fields from the Transaction object do you want to import?

You can select one or more additional fields from the Transaction object. These are then added to the Financial Balances, Financial Matching and Financial Transactions datasets. You must assign read access permission to the Integration User to add user-generated additional fields to these datasets. When you import packaged additional fields, they are prefixed with the originating object's name, unless this is already present in the field name. Lookup packaged fields are appended with 'Name', and ID fields are appended with 'ID', unless already present in the field name.

Note:

Encrypted and multi-select drop-down custom fields are not supported. These fields are not displayed in the list of available fields for import.

The following system-generated fields are not displayed in the list of available fields for import:

  • Apex Job ID
  • Archive Set
  • Avalara Integration Status
  • Avalara VAT Reporting Status
  • Batch Process
  • External ID
  • Invoice Group
  • Income Schedule Group
  • Unit of Work

To avoid duplication of fields stored on the Transaction Line Item object, you cannot add these fields from the Transaction object:

  • Account
  • Company
  • Document Number
  • Period
  • Year
4b. Which additional fields from the Transaction Line Item object do you want to import?

You can select one or more additional fields from the Transaction Line Item object. These are then added to the Financial Balances, Financial Matching, and Financial Transactions datasets. You must assign read access permission to the Integration User to add user-generated additional fields to these datasets. When you import packaged additional fields, they are prefixed with the originating object's name, unless this is already present in the field name. Lookup packaged fields are appended with 'Name', and ID fields are appended with 'ID', unless already present in the field name.

Note:

Encrypted and multi-select drop-down custom fields are not supported. These fields are not displayed in the list of available fields for import.

The following system-generated fields are not displayed in the list of available fields for import:

  • Apex Job ID
  • Archive Set
  • Avalara Integration Status
  • Avalara VAT Reporting Status
  • Batch Process
  • External ID
  • Invoice Group
  • Income Schedule Group
  • Unit of Work
5a. Do you want to create the Billing Contracts dataset?

Your Billing Central data is added to the Billing Contracts dataset. This requires access to Billing Central objects and fields in your org. If you want to use the Subscription Bookings dashboard, you must have configured the Opportunity to Contract Integration in Billing Central.

Note:

This question only appears if the Billing Central package is installed in your org and the Integration User and the user creating the app have a license for this package. If you configured your Analytics app before enabling Billing Central in your org, reconfigure the app to activate this feature.
5b. Do you want to include the amount of revenue recognized for billing contract line items?

If you select "Yes", the Contract Line Item Revenue Recognized field is added to the Billing Contracts dataset.

The source of this field is determined using your Revenue Management settings. The source is defined in the Recognized to Date Value field on the settings record for the Billing Contract Line Item object.

This requires access to Revenue Management objects and fields in your org. It also requires access to the field that contains the value on the Billing Contract Line Item object. Both you and the Integration User must have Billing Central and Revenue Management licenses, as well as access to the relevant objects and fields.

Note:

If multiple Revenue Management settings records for the Billing Contract Line Item object are defined in your org, you must ensure that they all have the same value set for Recognized to Date Value field.
5c. Which additional fields from the Contract object do you want to import?

You can select one or more additional fields from the Contract object. These are then added to the Billing Contracts dataset. You must assign read access permission to the Integration User to add user-generated additional fields to these datasets. When you import packaged additional fields, they are prefixed with the originating object's name, unless this is already present in the field name. Lookup packaged fields are appended with 'Name', and ID fields are appended with 'ID', unless already present in the field name.

Note:

Encrypted and multi-select drop-down custom fields are not supported. These fields are not displayed in the list of available fields for import.

5d. Which additional fields from the Contract Line Item object do you want to import?

You can select one or more additional fields from the Contract Line Item object. These are then added to theBilling Contracts dataset. You must assign read access permission to the Integration User to add user-generated additional fields to these datasets. When you import packaged additional fields, they are prefixed with the originating object's name, unless this is already present in the field name. Lookup packaged fields are appended with 'Name', and ID fields are appended with 'ID', unless already present in the field name.

Note:

Encrypted and multi-select drop-down custom fields are not supported. These fields are not displayed in the list of available fields for import.

6. How many overdue day ranges do you require for your aged analysis reports? Reports include a Current column by default, which contains all transactions that are not yet due. For example, the default value is "5" and creates the following age ranges: 1-30, 31-60, 61-90, 91-120, 121+. You can change the days in each range on your report.
7. Do you want to create the Recognition Transactions dataset?

Your Revenue Management data is added to the Recognition Transactions dataset. This requires access to Revenue Management objects and fields in your org. If you want to use the Deferred Revenue Reconciliation dashboard you must answer "Yes" in response to Question 7 to create the Billing Documents dataset.

Note: This question only appears if the Revenue Management package is installed in your org and the Integration User and the user creating the app have a license for this package. If you configured your Analytics app before enabling Revenue Management in your org, reconfigure the app to activate this feature.
8. Do you want to create the Billing Documents dataset?

Your Billing Central data is added to the Billing Documents dataset. This requires access to Billing Central objects and fields in your org. If you want to use the Deferred Revenue Reconciliation dashboard you must answer "Yes" in response to question 6 to create the Recognition Transactions dataset.

Note: This question only appears if the Billing Central package is installed in your org and the Integration User and the user creating the app have a license for this package. If you configured your Analytics app before enabling Billing Central in your org, reconfigure the app to activate this feature.
9a. Do you want to create the Revenue Waterfall dataset?

Your Revenue Management and Billing Central data is added to the Revenue Waterfall dataset. This dataset requires access to Revenue Management and Billing Central objects and fields in your org. If you want to use the Deferred Revenue Waterfall dashboard, you must have configured the Revenue Schedules feature in Revenue Management.

Note: This question is only enabled if the Billing Central and the Fall 2020Revenue Management packages are installed in your org, and the Integration User and the user creating the app have licenses for these packages. You also need to ensure the Revenue Schedules feature is active in your org through the Feature Console and that the Integration User has permissions assigned to read the Billing Contract Line Item field in the Revenue Schedule object. If you configured your Analytics app before enabling Revenue Management or Billing Central in your org, reconfigure the app to activate this feature.
9b. Which additional fields from the Contract object do you want to import?

You can select one or more additional fields from the Contract object. These are then added to the Revenue Waterfall dataset. You must assign read access permission to the Integration User to add user-generated additional fields to these datasets. When you import packaged additional fields, they are prefixed with the originating object's name, unless this is already present in the field name. Lookup packaged fields are appended with 'Name', and ID fields are appended with 'ID', unless already present in the field name.

Note:

Encrypted and multi-select drop-down custom fields are not supported. These fields are not displayed in the list of available fields for import.

9c. Which additional fields from the Contract Line Item object do you want to import?

You can select one or more additional fields from the Contract Line Item object. These are then added to the Revenue Waterfall dataset. You must assign read access permission to the Integration User to add user-generated additional fields to these datasets. When you import packaged additional fields, they are prefixed with the originating object's name, unless this is already present in the field name. Lookup packaged fields are appended with 'Name', and ID fields are appended with 'ID', unless already present in the field name.

Note:

Encrypted and multi-select drop-down custom fields are not supported. These fields are not displayed in the list of available fields for import.

10. Do you want to append your additional field labels with a suffix? You can choose whether to append your additional fields with a suffix. This suffix indicates that they are additional fields, and the object they are derived from. For example, a custom field "Location" from the Transaction object would have the name "Location [TransCustomField]".
11a. Do you want to create the Order and Inventory Management dataset?

Your Order and Inventory Management data is added to the Order and Inventory Management dataset. This requires access to Order and Inventory Management objects and fields in your org. If you want to use the Item Overview, Order Management, and Procurement dashboards you must answer "Yes" in response to Question 9 to create the Order and Inventory Management dataset.

Note:

You can only select "Yes" if Order and Inventory Management is installed in your org and if both you and the Integration User have a license for this package. If you configured your Financial Analytics app before enabling Order and Inventory Management in your org, reconfigure the app to activate this feature.
11b. Do you want to include the amount of revenue recognized and the amount of cost amortized for sales order line items?

If you select "Yes", the Sales Order Line Item Revenue Recognized and Sales Order Line Item Cost Amortized fields are added to the Order and Inventory Management dataset.

The source of these fields is determined using your Revenue Management settings for the Sales Order Line Item object. The source for Revenue Recognized is defined in the Recognized to Date Value field and the source for Cost Amortized is defined in the Amortized to Date Value field.

This requires access to Revenue Management objects and fields in your org. It also requires access to the fields that contain the values on the Sales Order Line Item object. Both you and the Integration User must have Order and Inventory Management and Revenue Management licenses, as well as access to the relevant objects and fields.

Notes:
  • If the Amortized to Date Value field is not populated on the Revenue Management settings record, the Sales Order Line Item Cost Amortized is not added to the dataset. Similarly, if Revenue Recognized to Date Value is not populated on the settings record, the Sales Order Line Item Revenue Recognized is not added to the dataset.
  • If multiple settings records for the Sales Order Line Item object are defined in your org, you must ensure that they all have the same values set for the Recognized to Date Value and Amortized to Date Value fields.
12. Do you want to import Fixed Asset Management data? This step adds your Fixed Asset Management data to the Financial Transactions and Financial Balances datasets. This requires access to Fixed Asset Management objects and fields in your org.
13. Do you want to import Planning data? This step adds your Planning and Analysis data to the Financial Transactions and Financial Balances datasets. This requires the Integration User to have access to Planning and Analysis objects and fields in your org.

You must now configure your KPIs. For more information see Setting up Your Dashboards.

Note:

When including any additional fields to your datasets (questions 3a, 3b, 4b, 4c, 8b, and 8c in the configuration wizard), you must ensure that the "Text Area (Long)" custom field contains no more than 32,000 characters.

If you create an app which includes additional fields and later delete these fields on the objects where you retrieved them from, the app retains the fields. You must remove the fields (questions 3a, 3b, 4b, 4c, 8b, and 8c) from the app template by re-running the configuration wizard.

When you run the configuration wizard to create an app, a recipe and a dataflow is generated. The recipe and dataflow are named according to the app name you provide. The following dashboards, datasets, and lenses are generated:

Financial Analytics Generated Assets
Dashboards Datasets Lenses
  • Aged Analysis by Date
  • Aged Analysis by Period
  • Budget Comparison
  • CFO Balance Sheet Detail
  • CFO Balance Sheet Trend Prediction
  • CFO Profitability Detail
  • CFO Profitability Trend Prediction
  • Deferred Revenue Waterfall
  • Item Overview
  • Order Management
  • Procurement
  • Subscription Bookings
  • Transaction List
  • Trial Balance
  • Billing Contracts
  • Billing Documents
  • Currencies
  • Financial Accounts
  • Financial Balances
  • Financial Matching
  • Financial Periods
  • Financial Transactions
  • Recognition Transactions
  • Revenue Waterfall
  • Order and Inventory Management
  • Churn ARR
  • Churn MRR
  • Contract Adjustments ARR
  • Contract Adjustments MRR
  • Down Sell ARR
  • Down Sell MRR
  • Ending ARR
  • Ending MRR
  • FBTB011 Trial Balance (Open/Close)
  • FBTB031 Trial Balance with Adjustments
  • Localization Financial Statements
  • Net New ARR
  • Net New MRR
  • Renewals ARR
  • Renewals MRR
  • Starting ARR
  • Starting MRR
  • Unaccounted Error ARR
  • Unaccounted Error MRR
  • Upsell ARR
  • Upsell MRR
Notes:
  • The Currencies dataset is only available if your org is configured for multiple currencies.
  • By default, all the dashboards in the Financial Analytics apps, except for Order Management, are configured to display values in the same currency that the Integration User had assigned during the app creation. To ensure that the dashboards work properly, you must set the Integration User's currency to your corporate currency before creating the app.
  • Añadir info sobre data combination if XPNA está instalado.

Additionally, if you have enabled and configured Einstein Discovery in your org, the following stories are generated:

Generated Discovery Stories

Package

 App Template

Stories
Business Analytics Financial Analytics
  • Days to Pay