Pages

Friday, October 19, 2018

Salesforce Inbox License

We did write how a blog on how to check Einstein Analytics License Assignment, this blog will share about checking Inbox license in Salesforce Classic and Lightning.

Inbox License Assignment are pretty similar to Einstein Analytics License Assignment, you can see how many Inbox total licenses you have, how many licenses used and remaining licenses in Company Information under Permission Sets Licenses in the setup menu.



Next question, I would like to see who has this licenses assigned? If you are in Lightning, this is pretty simple, search for Inbox in the setup menu and you will see Users and Licenses.



But, how about if I am still in Classic? short answer, flip to Lightning :) anyway, you can run SOQL to get the user if you are still in Classic, here you go

SELECT Name, Id FROM User WHERE Id IN
(SELECT AssigneeId FROM PermissionSetLicenseAssign WHERE PermissionSetLicense.MasterLabel ='Inbox') AND IsActive=true
ORDER BY Name


Next, if I manually open the user detail, how I can see if the license has been assigned? Is it under Permission Set Assignments or Permission Set License Assignments related list? This is exactly the same with Einstein Analytics licenses assignment, once you add the Permission Set, the Permission Set License will be auto added, but not the other way round.


From above screenshot, once you add "Inbox With Einstein Activity Capture" permission set, Inbox license will be auto-granted.


Reference:


Thursday, October 4, 2018

Einstein Activity Capture

Einstein Activity Capture is introduced on Summer '18 release, it is free up to 100 licenses for org with Sales Cloud license. When sales rep connects their Google™ or Microsoft® account to Salesforce, activities from those accounts show up on business and person accounts, contacts, leads, opportunities, quotes, and contracts in Salesforce. Plus, reps get read-only access to the Activities dashboard, which lets them view a summary of sales activities.

Step to enable Einstein Activity Capture:

1. Activate Einstein Activity Capture
Reach out to Salesforce Support to enable Einstein Activity Capture. Once enabled, you should see Einstein Activity Capture under the setup menu.




Then, enable Einstein Activity Capture from Setting menu.



2. Assign Permission Set to user
You need one of the following Permission Set depends on your license:
License = Sales Cloud Einstein --> Permission Set = Sales Cloud Einstein  
License = Inbox --> Permission Set = Inbox with Einstein Activity Capture
License = Sales Cloud --> Permission Set = Standard Einstein Activity Capture


3. User Setup
Once the permission set given to the user, the user needs to configure it from their setup menu. Click username from the top right corner, click Settingslooks for Einstein Activity Capture, then click Settings




It will popup Meet Inbox window, then click Next and follow the wizard. 



Then, select a Google or Microsoft account to connect.




Once account added, it will be shown in Connected Account under user Einstein Activity Capture setup menu.



Here you have the option if you want to share the emails and events to everyone, my groups, and only me, in this sample, I select Everyone.


4. The Moment of Truth

Sending an email out using your email client to Contact or Lead
Based on the email sent out, Salesforce will automatically tag the email to the Contact or Lead as Past Activities. You need to make sure the email address in Salesforce is correct.




Contact reply your email
When your contact email you and his/her email address is in Salesforce, the email will auto added as Past Activities too.




What happened if more than one Lead or Contact with the same email address? 
The email correspondence will be linked to all Contact and Lead.


Reference:


Monday, September 10, 2018

Einstein Analytics: Embed Dashboard to Salesforce Classic

As you see in the previous blog Embed Report Chart to Page Layout, adding report charts to record detail page is pretty simple. But, embedding Einstein Analytics dashboard to record detail page is different.

You can add Einstein Analytics dashboard to record detail page similar with Report Chart in Classic, but it will not show when you open the same record in Lightning. In this blog, I'll share on adding Einstein Analytics dashboard to record detail page in Classic only.

When you edit the page layout, notice "Wave Analytics Assets" and all available dashboard can be added to the page layout.

But, not as simple as adding report charts to the page layout, when adding Einstein Analytics dashboard to the page layout to show relevant record being viewed, you need to play a bit with JSON to link record Id to Einstein Analytics dashboard.

Here is the complete format of JSON to add in the field mapping, all words in yellow highlight are keywords.
"datasets": {
    "dataset1": [
        {"fields": ["field1"],
           "selection": ["$selection1", "$selection2"],
           "filter": {"operator": "operator1", "values": [["$value1, $value2"], ["$value3", "$value4"]]}
        },
        {"fields": ["field2", "field3"],
           "selection": ["$selection3", "$selection4"]
        }
    ],
    "dataset2": [
        {"fields": ["field4"],
           "filter": {"operator": "operator2", "values": ["$value5"]}
        }
    ]
}

Sample: when open account page, auto filter Einstein Analytics dashboard with Account being viewed. Add the JSON into Field mapping of Asset Properties.



Let us analyze the JSON code:
1:  {  
2:   "datasets": {  
3:     "OptyWithAcct": [  
4:      { "fields": ["AccountId"],  
5:        "selection": ["$Id"]  
6:      }  
7:     ]  
8:   }  
9:  }  
- line 2: datasets is the keyword, nothing to change
- line 3: OptyWithAcct is the dataset name
- line 4: fields is a keyword, AccountId is API field name in the dataset
- line 5: selection is a keyword, $Id is the API field name from the object, not from the dataset


Let us see the result:


1. The dashboard is automatically filtered with current Account Id.
2. You need to have Account Id as list filter in the dashboard, otherwise, we can't filter the dashboard.


ReferenceEmbed Analytics Dashboards in Salesforce Classic Pages



Salesforce: Embed Report Chart to Page Layout

Adding a chart from report to record page is pretty simple, as long as you have permissions to create reports, store report to the public folder, and permission to edit record page layout.

Here are few items to check when embedding report chart to object page:
- the report is in a folder that’s shared with users who need access, not in private folder.
- the source report format is summary or matrix.
- the source report has a chart.

You can follow this document to add report chart to a page layout Add a Report Chart to a Page Layout.

Usually, when you embed report charts to page layout, you want to show the relevant data to the current record, such as Total Opportunity Amount by Stage for current Account, for this case, you can use Opportunity standard report type, as Account Id is available in Opportunity report type.

Note: for this scenario, Account Id or Account Name does not need to be present in the report.

When editing the page layout to add report chart, you can select the chart size, appearance, data refresh, and the data filter. Check out this document Filtering Report Charts to Show Data Relevant to the Page.



However, you can add only up to two report charts on a page. The good news, embedded Report Chart in page layout will work in both Classic and Lightning, even you can't see the Refresh button in Lightning, so the best option is to enable "Refresh each time a user opens the page" in the chart properties.



Reference:



Sunday, September 9, 2018

Einstein Analytics: How to rename Dataflow

Dashboard
You can change dashboard label/title, by open the dashboard click edit, then click the pencil icon next to the title to change it.



Or, by open the dashboard in JSON mode, then change the "label", by default, it would be at the 2nd row, but to get the dashboard API name, follow this blog Dashboard API Name.



Remember you need to save the dashboard for both above options. Another method to change dashboard label is, when you click Save icon to save dashboard, the system will pop up a window and you can change dashboard title from here (this will rename dashboard, not save as a new dashboard).



Lens
To change lens label, open the Lens in JSON mode, you will find them at the top, by default, it would be at 3rd row from the top with "label", remember to save the lens. When you edit Lens in JSON, you will see Lens name too, but unfortunately, you can't save it.

Same as the dashboard, you can rename lens title when click Save icon, change lens title will rename the lens, not save as a new lens.


Dataset
Similar to the dashboard, to rename Dataset label, edit the dataset, then click the pencil icon next to the title to change it. When you edit the dataset, you also can move the dataset to the new app.



App
To rename an app, simply open the app, then click the pencil icon next to the title to change it. 



Dataflow
As of Winter '19 release, we cannot rename dataflows. When edit a dataflow, it will not give us the option to change dataflow name/title. You can vote this idea in IdeaExchange.

However, if you really need to change the dataflow label, here is the workaround:
- Download Dataflow JSON to your local computer
- Create new Dataflow
- Click "Upload JSON" button and upload downloaded JSON file
- Click "Update Dataflow" button to save
- Once the new dataflow is verified, delete the old dataflow.




Wednesday, September 5, 2018

Case-sensitive VLOOKUP for Salesforce Record Id

Salesforce record Id will always return 15 characters across all objects, and the Id is case sensitive. Of course, if you have admin access, you can create a formula field CASESAFEID(Id) and this will return 18 characters which are case-insensitive.

But, if you have to work with case-sensitive 15 characters and do VLOOKUP in Excel, you need to do extra work, as you probably know that one of the limitations of VLOOKUP is case-insensitive, it means the case is not a consideration in the lookup process, example: 0038000001c9YsM is essentially the same as 0038000001c9Ysm. Hence, VLOOKUP will consider that they are the same and return the first matched, which is totally wrong.

There are a few options you can do for VLOOKUP:

1. Convert 15 to 18 characters
We have shared this in a blog Convert ID from 15 to 18 characters with Excel formula, so you need to have an additional column in the source and lookup data, and use that column for VLOOKUP.

2. Convert to ASCII
This is pretty similar to option 1 above, instead of converting 15 characters case-sensitive to 18 characters case-insensitive, we convert the record Id into ASCII using CODE()Microsoft Excel CODE function returns the ASCII value of a character or the first character in a cell.

=CODE(MID(A2,1,1)) & CODE(MID(A2,2,1)) & CODE(MID(A2,3,1)) & CODE(MID(A2,4,1)) & CODE(MID(A2,5,1)) & CODE(MID(A2,6,1)) & CODE(MID(A2,7,1)) & CODE(MID(A2,8,1)) & CODE(MID(A2,9,1)) & CODE(MID(A2,10,1)) & CODE(MID(A2,11,1)) & CODE(MID(A2,12,1)) & CODE(MID(A2,13,1)) & CODE(MID(A2,14,1)) & CODE(MID(A2,15,1))

You need to convert both source and column data Record Id to ASCII, then use it for VLOOKUP().


Reference:



Sunday, August 5, 2018

Einstein Analytics: Dashboard API Name

As usual Salesforce stuff, we have label and name (read API name) for an object, field, dashboard, and etc. But, is there such things in the Einstein Analytics for the dashboard? Yes, there is, although you do not always need to know the API name, however, in some scenario, you need to know.

When you edit a dashboard, you only change the title, same goes to the lens. Let looks at dashboard JSON, the second line of the dashboard will say "label": "dashboard name", we can easily change the label, but can we get the dashboard API name?

Scenario: I create a dashboard called "backup map", by default the API name would be backup_map, this is just by replacing space with _.
After a while, I change the label from "backup map" to "my map", will the API name change from backup_map to my_map? The answer is No.

Here 2 options can be used to get dashboard API name:

1. Use Link Widget
Create a new dashboard, add link widget and select link to Saved dashboard, and select the dashboard you would like to check.



Now, open dashboard JSON, and looks for link_1 (for this sample) widget, here we go:
       "widgets": {
            "link_1": {
                "type": "link",
                "parameters": {
                    "destinationType": "dashboard",
                    "includeState": false,
                    "text": "Button title",
                    "textColor": "#44A2F5",
                    "textAlignment": "center",
                    "fontSize": 12,
                    "destinationLink": {
                        "name": "backup_map"
                    }
                }
            }
        },


2. Workbench
Workbench is a powerful tool, love by all Salesforce developer and admin, also for us as Einstein Analytics power user.

Once you login to Workbench, navigate to utilities - REST Explorer, change the URI to /services/data/v43.0/wave/dashboards then click Execute button, then click Expand All link. Here, you will find everything you need to know about your dashboards. From the screenshot below, the API name is "backup_map", while the label has been changed to "my map".



You can also evaluate other stuff in Einstein Analytics by changing the URI to /services/data/v43.0/wave/





Salesforce Lightning: Log a Call button does not appear in Activity component

For those of you have been migrated from Classic to Lightning, you notice that "Open Activities" and "Activity History" are no longer appeared in the related list, instead, they appear as a Ligthning component called Activity. Log a Call, New Task, and New Event will not show as buttons anymore, but as tabs under Activity component, as they appear as a component, users can enter the data without leaving the main detail page.


However, if you don't see those tabs under Activity component, here are few things you should check:

1. Page Layout
Yes, I am referring to Classic page layout, not Lightning Page. If you have multiple page layout based on profile or record type or both. Make sure you are checking the correct page layout.

Open a record, click the gear icon, then Edit Page link, click Details tab, then click the layout in Details tab, check the page layout name with (previewed).



Now, go to that page layout -- back to the record page, click Edit Object link under the gear icon, select Page Layouts menu, then click the same page layout showed in the previewed earlier.

Select Mobile and Lightning Actions, make sure Log a CallNew Task, and New Event are added into the Salesforce Mobile and Lightning Experience Actions section.



2. Record Type
Check if you have record type defined (even only one) in Task and Event, make sure they are selected in the global action because of one action only for one record type.



Go to Global Actions under Setup menu, click edit on Log a Call, you may see this by the standard.
In the Record Type, change --Master-- to Special, and click Save button.



Now, back to the record page and check Activity component, you should see Log a Call action appear under Activity component. The same for New Task action, it should appear too once you fix the Global Action.



For New Event action (as it is Event object), check if you have Record Type defined in the Event, if yes, you need to do the same for New Event action to define the Record Type.


Reference:



Wednesday, August 1, 2018

Einstein Analytics: Connect Date Source with Date

In previous blog Connect Data Sources and Binding between Dataset, we share about using Connect Data Sources and binding to connect dataset. This blog will share tips:
- how to connect data sources between Date and Dimension.
- how to create list value using Date field


Use Case 1: Sales date is stored in Actual dataset, while Target amount is in Target dataset. We would like to show both actual and target in a dashboard when a certain month and year are selected.

Steps:
1. Target data
Load Year and Month as 2 fields, load both fields as Dimension, not as Measure (Number).

2. Add List
Add List for both Year and Month to the dashboard.

3. Connect Data Source for Month
For Data Source 1, select Month from Target -- here Month is Dimension. For Data Source 2, we can't select Date or type Date_Month from Actual (it is a Date field), so just select any Dimension field for temporary, in this sample, I select Sales_Rep. My dataset API name for Target is Text_Month, and for Actual is Sales_by_Date.


4. Edit dashboard JSON
Einstein Analytics by default will auto parse date field into many fields, e.g. FieldName_Year, FieldName_Month, FieldName_Date, and other FieldName_xxx, we can connect target Month with FieldName_Month by editing dashboard JSON, change the temporary Dimension field name Sales_Rep with Date_Month.

5. Connect Data Source for Year
From dashboard JSON, copy and paste in from Month, and change to Year as a newly connected data source.

       "dataSourceLinks": [
            {
                "fields": [
                    {
                        "dataSourceName": "Text_Month",
                        "dataSourceType": "saql",
                        "fieldName": "Month"
                    },
                    {
                        "dataSourceName": "Sales_by_Date",
                        "dataSourceType": "saql",
                        "fieldName": "Date_Month"
                    }
                ],
                "label": "Month",
                "name": "Link_4521"
            },
            {
                "fields": [
                    {
                        "dataSourceName": "Text_Month",
                        "dataSourceType": "saql",
                        "fieldName": "Year"
                    },
                    {
                        "dataSourceName": "Sales_by_Date",
                        "dataSourceType": "saql",
                        "fieldName": "Date_Year"
                    }
                ],
                "label": "Year",
                "name": "Link_4522"
            }
        ]



6. The moment of Truth




Use Case 2: Target is stored as a Date field.

Steps:
1. Add List
Add List for both Year and Month to the dashboard, you cannot select Date field for List, so just select any Dimension field temporary.

2. Edit List
Edit the List and change the Bars by selecting Date then Month for Month list, and select Date then Year for Year list.


You also can manually edit dashboard JSON, looks the query and change the group to Date_Month for month list, and Date_Year for the year list.

                "query": {
                    "groups": [
                        "Date_Year"
                    ],
                    "measures": [
                        [
                            "count",
                            "*"
                        ]
                    ]
                }

When you go back to edit the widget, notice that now it group by Date (Year) or Date (Month) for each list.



3. Connect Data Source for Month 
Because you can't select Year and Month from both target and actual, just select any Dimension field as a temporary placeholder, edit dashboard JSON and change with Date_Month for both data source. Copy from Month to Year. My dataset API name for Target is Target, and for Actual is Sales_by_Date.

            {
                "name": "Link_2009",
                "label": "Date_Year",
                "fields": [
                    {
                        "fieldName": "Date_Year",
                        "dataSourceName": "Sales_by_Date",
                        "dataSourceType": "saql"
                    },
                    {
                        "fieldName": "Date_Year",
                        "dataSourceName": "Target",
                        "dataSourceType": "saql"
                    }
                ]
            },
            {
                "name": "Link_2010",
                "label": "Date_Month",
                "fields": [
                    {
                        "fieldName": "Date_Month",
                        "dataSourceName": "Sales_by_Date",
                        "dataSourceType": "saql"
                    },
                    {
                        "fieldName": "Date_Month",
                        "dataSourceName": "Target",
                        "dataSourceType": "saql"
                    }
                ]
            }



4. The moment of Truth





Monday, July 30, 2018

Einstein Analytics: Getting started with XMD

XMD stands for Extended Metadata, it enables you to customize the formatting of dataset fields and their values in Analytics dashboards and lenses. If you modify the XMD for a dataset, every UI visualization that uses the dataset shows the modified format.

You can customize the following with XMD:
  • Format measures. Example: Show the decimal and grouping separators for currency.
  • Add prefixes and suffixes to measures. Example: Show the percent symbol (%) after each percentage.
  • Multiply measures by a factor. Example: Multiply by 100 to convert a decimal to a percent.
  • Change display labels for dimensions and measures.
  • Customize colors in charts based on field values.
  • Define the first day of the week for the calendar year.
  • Add action menus to dimensions that let dashboard viewers invoke actions from lenses and dashboards.
Once a dataset created, by default the XMD will have no values, let's look at this. You can download XMD (which is also in JSON format) by editing the dataset.


Open the JSON file and here is the content
{"dataset":{},"dates":[],"derivedDimensions":[],"derivedMeasures":[],"dimensions":[],"measures":[],"organizations":[],"showDetailsDefaultFields":[]}

Tips: use jsoneditoronline.org to reformat the file into a human-friendly format
{
  "dataset": {},
  "dates": [],
  "derivedDimensions": [],
  "derivedMeasures": [],
  "dimensions": [],
  "measures": [],
  "organizations": [],
  "showDetailsDefaultFields": []
}


In this blog, I'll share how to rename field name with XMD for all dashboard and lenses, or in particular dashboard with SAQL.


Setup field format and label
Let us format Amount field to be in currency format $9,999.99
- Click the Dataset to open as a Lens
- Click Fields

- Set Amount format

- Rename label Amount to Initial Amount, and Region to Sales Region
- Click Save button
- Change the Lens into Values Table and now you will see Amount is in currency format with header Initial Amount and Region become Sales Region

Note that this change will change all existing dashboard and lens.



Back to XMD
Let's us re-download the XMD file and see what how it looks like now:
{
  "dataset": {},
  "dates": [],
  "derivedDimensions": [],
  "derivedMeasures": [],
  "dimensions": [
    {
      "conditionalFormatting": {},
      "customActions": [],
      "field": "Region",
      "label": "Sales Region",
      "members": [],
      "recordDisplayFields": [],
      "salesforceActions": []
    }
  ],
  "measures": [
    {
      "conditionalFormatting": {},
      "field": "Amount",
      "format": {
        "customFormat": "[\"$#,##0.00\",1]"
      },
      "label": "Initial Amount"
    }
  ],
  "organizations": [],
  "showDetailsDefaultFields": []
}

** you can use jsoneditoronline.org to re-format it.


Edit Amount with SAQL
In case that we need to change the Amount header for a particular dashboard, you can edit the lens/widget with SAQL. In this example, we are going to change from Initial Amount to MRR.
- Open the dataset with Lens
- Change to Values Table
- Click SAQL Mode button

If you notice now MRR does not have currency format we have set earlier. To enable this, we need to edit the XML file again. We need to add following conditional formatting in XMD under derivedMeasures.

A measure is a quantitative value, like revenue and exchange rate. You can do the math on measures, such as calculating the total revenue and minimum exchange rate.

Derivated measures are the ones that you get from the measures, it is calculated fields so they don’t really exist in your dataset.

{
  "dataset": {},
  "dates": [],
  "derivedDimensions": [],
  "derivedMeasures": [
  {
      "conditionalFormatting": {},
      "field": "MRR",
      "format": {
        "customFormat": "[\"$#,##0.00\",1]"
      },
      "label": "MRR"
    }
  ],
  "dimensions": [
    {
      "conditionalFormatting": {},
      "customActions": [],
      "field": "Region",
      "label": "Sales Region",
      "members": [],
      "recordDisplayFields": [],
      "salesforceActions": []
    }
  ],
  "measures": [
    {
      "conditionalFormatting": {},
      "field": "Amount",
      "format": {
        "customFormat": "[\"$#,##0.00\",1]"
      },
      "label": "Initial Amount"
    }
  ],
  "organizations": [],
  "showDetailsDefaultFields": []
}


Upload back the XMD file from Replace menu in Dataset edit. Let's reload the lens/widget.



Now realize that Amount now called MRR for the particular lens and it has current formatting too. Check Fields from Lens and now MRR is added as Derived Measures



As you see, actually we can add Derived Measures directly when you edit the dataset from the lens, without the need to edit the XMD manually.




Reference


Friday, July 27, 2018

Einstein Analytics: Chart Type Binding

In the blog shared earlier Einstein Analytics: The quest for Binding in Dashboard, we discussed in a glance that we can let user change the type of chart on the fly by using binding, it will work for most of the chart type, but not all, this is because specific chart need to have additional parameters, such as for Heatmap chart type, it requires highColor and lowColor.



Let's see the steps and sample:

1. Add a chart to the dashboard and select the initial chart type.

2. Add static step with values of chart type, such as Stack Vertical Bar, Stack Horizontal Bar, etc. You need to know the value for each chart type, sample
              "values": [
                    {
                        "display": "Stack Vertical Bar",
                        "value": "stackvbar"
                    },
                    {
                        "display": "Stack Horizontal  Bar",
                        "value": "stackhbar"
                    },
                    {
                        "display": "Heatmap",
                        "value": "heatmap"
                    },
                    {
                        "display": "Line",
                        "value": "line"
                    }
                ]

3. Change columnMap to null, you need to change only columnMap under chart/widget (not the one under the step).

4. Change visualizationType under chart/widget (not the one under the step) to {{coalesce(cell(Chart_Type_1.selection, 0, \"value\"), cell(Chart_Type_1.result, 0, \"value\")).asString()}}
** Chart_Type_1 is the step name for static step

5. For some type of charts, they required additional parameters, you need to add them, otherwise, it will not work. You can monitor the additional parameters when you add a chart with the selected chart type, some of the parameters are required, and some are not required.

all values in parameters below are for samples only

Heatmap
  "lowColor": "#E2F4FC",
  "highColor": "#009DDF",
  "x": {
          "showAxis": true,
          "showTitle": true,
          "title": ""
       },
  "y": {
          "showAxis": true,
          "showTitle": true,
          "title": ""

       }


Horizontal Bar, Vertical Bar, Stack Horizontal Bar, Stack Vertical Bar
  "trellis": {
                       "enable": false,
                       "showGridLines": true,
                       "flipLabels": false,
                       "type": "x",
                       "chartsPerLine": 4,
                       "size": [
                           100,
                           100
                        ]
             },
  "showValues": true,
  "axisMode": "multi",
  "dimensionAxis": {
                        "showAxis": true,
                        "showTitle": true,
                        "title": "",
                        "customSize": "auto",
                        "icons": {
                            "useIcons": false,
                            "iconProps": {
                                "column": "",
                                "fit": "cover",
                                "type": "round"
                            }
                        }
                    },
  "measureAxis1": {
                        "sqrtScale": false,
                        "showAxis": true,
                        "customDomain": {
                            "showDomain": false
                        },
                        "showTitle": true,
                        "title": ""
                    },
                    "measureAxis2": {
                        "sqrtScale": false,
                        "showAxis": true,
                        "customDomain": {
                            "showDomain": false
                        },
                        "showTitle": true,
                        "title": ""

                    },
  "normalize": false,

  "exploreLink": true


Line
  "showPoints": false,
  "showZero": true,
  "drawArea": {
                        "showDrawArea": false,
                        "bounding1": "",
                        "bounding2": "",
                        "measure": ""
              },
  "dashLine": {
                        "showDashLine": false,
                        "measures": ""

              },
  "exploreLink": true


Donut
  "trellis": {
                        "enable": false,
                        "showGridLines": true,
                        "flipLabels": false,
                        "type": "x",
                        "chartsPerLine": 4,
                        "size": [
                            100,
                            100
                        ]
            },
  "exploreLink": true,
  "showMeasureTitle": true,
  "centerValueType": "number",
  "centerText": "",
  "inner": 60


In summary: if your binding contains such chart type, make sure to add all of them to the parameters, especially the required parameters, otherwise, the binding for that chart type will just not working.