September 19 Release Notes

Reporting: Full Screen Mode Available in Spotlight

You now have the ability to display Model Manager, Views, and Reports in full screen mode; providing more screen real estate.

Access Spotlight from PCR or a browser. Click the Modeling icon and select Analyze, Report, or Model.

On each of the application pages (Analyze, Report, and Model), click the full screen icon shown below.

Once full screen mode is displayed, select the escape button on your keyboard to return to regular mode, or click the Exit Full Screen button shown below.

Reporting: Enhanced Dynamic Report Search Behavior

Contact Host Analytics Support to enable this feature in your Production environment.

With this release, the search behavior in the Members section of Dynamic Report has been enhanced. Now, when you search for a member, the member hierarchy is displayed along with the search result.

For example, if you want to search for Executive, the search result is displayed along with the member hierarchy, as shown in the image below.

Prior to this release, only the search result was displayed, as shown in the image below.

Modeling: Export Dimension Hierarchy (Master and Analytic Models)

This API allows you to export the entire dimension hierarchy from a specified model in XML format. The following data is exported:

• Hierarchy member code

• Hierarchy member parent

• Hierarchy member rollup operator

• Hierarchy member display label

POST /api/modeling/model/dimension/export HTTP/1/1

Content-Type: application/xml

Accept: application/xml

X-ACCESS-TOKEN:

Request Payload

<?xml version="1.0" encoding="UTF-8"?>

<payload>

<model>$ModelName</model>

<dimension>$DimensionName</dimension>

</payload>

Parameters

1. $ModelName: (type: string) Name of the model. If the model specified does not exist, the operation is canceled.

2. $DimensionName: (type: string) Name of the Dimension that is associated with this model. If the dimension specified does not exist, the operation is canceled.

Payload Sample

<?xml version="1.0" encoding="UTF-8"?>

<payload>

<model>Sample_Model</model>

<dimension>account</dimension>

</payload>

Response

<?xml version="1.0" encoding="UTF-8"?>

<Payload>

<Dimension-Member>

<Member-Code>Net Income</Member-Code>

<Rollup-Operator>+</Rollup-Operator>

<Display-Label>Net Income</Display-Label>

</Dimension-Member>

<Dimension-Member>

<Member-Code>Income</Member-Code>

<Member-Parent>Net Income</Member-Parent>

<Rollup-Operator>+</Rollup-Operator>

<Display-Label>Income</Display-Label>

</Dimension-Member>

<Dimension-Member>

<Member-Code>Bookings</Member-Code>

<Member-Parent>Income</Member-Parent>

<Rollup-Operator>+</Rollup-Operator>

<Display-Label>Bookings</Display-Label>

</Dimension-Member>

<Dimension-Member>

<Member-Code>Subscription</Member-Code>

<Member-Parent>Income</Member-Parent>

<Rollup-Operator>+</Rollup-Operator>

<Display-Label>Subscription</Display-Label>

</Dimension-Member>

<Dimension-Member>

<Member-Code>Expenses</Member-Code>

<Member-Parent>Net Income</Member-Parent>

<Rollup-Operator>-</Rollup-Operator>

<Display-Label>Expenses</Display-Label>

</Dimension-Member>

<Dimension-Member>

<Member-Code>Rent</Member-Code>

<Member-Parent>Expenses</Member-Parent>

<Rollup-Operator>+</Rollup-Operator>

<Display-Label>Rent</Display-Label>

</Dimension-Member>

<Dimension-Member>

<Member-Code>Salary</Member-Code>

<Member-Parent>Expenses</Member-Parent>

<Rollup-Operator>+</Rollup-Operator>

<Display-Label>Salary</Display-Label>

</Dimension-Member>

<Dimension-Member>

<Member-Code>Bonus</Member-Code>

<Member-Parent>Expenses</Member-Parent>

<Rollup-Operator>+</Rollup-Operator>

<Display-Label>Bonus</Display-Label>

</Dimension-Member>

<Dimension-Member>

<Member-Code>Formula Accounts</Member-Code>

<Member-Parent>Net Income</Member-Parent>

<Rollup-Operator>~</Rollup-Operator>

<Display-Label>Formula Accounts</Display-Label>

</Dimension-Member>

<Dimension-Member>

<Member-Code>Ratio</Member-Code>

<Member-Parent>Formula Accounts</Member-Parent>

<Rollup-Operator>~</Rollup-Operator>

<Display-Label>Ratio</Display-Label>

</Dimension-Member>

<Dimension-Member>

<Member-Code>If Then Else</Member-Code>

<Member-Parent>Formula Accounts</Member-Parent>

<Rollup-Operator>~</Rollup-Operator>

<Display-Label>If Then Else</Display-Label>

</Dimension-Member>

</Payload>

Success Response

HTTP/1.1 200 OK

Error Responses

Service Not Available (Possibly due to maintenance)

HTTP/1.1 404 Not Found

One or more HTTP headers were missing

HTTP/1.1 412 Precondition Failed

Could not find payload body <payload>…</payload>

Could not find model: xxx

Could not find dimension: xxx

Dimension cannot be null or empty.

HTTP/1.1 412 Precondition Failed

Unauthorized Access (Access key lookup failed)

HTTP/1.1 401 Unauthorized

Invalid XML (Bad Request)

HTTP/1.1 400 Bad Request

Platform: Enabled Translations Data for the NetSuite Connect DLR

With this release, Translations data load has been enabled for the NetSuite Connect DLR. Now, you can load Translations data using the NetSuite Connect DLR.

You can select Translations Data from the Load Sub Item drop-down list in the New Data Load Rule step to load Translations Data from the NetSuite Connect DLR, as shown in the image below.

Platform: Allow Segment Properties through NetSuite Connect DLR

With this release, all the segment properties can be loaded from the NetSuite Connect DLR or you can select the values for the segment properties in the Define Overall Rule Settings step.

Prior to this release, a few segment properties were disabled. A predefined value was set in the Define Overall Rule Settings step for property and the user was not allowed to change the value while loading data.