Contents x
    July 19 Release Notes
    • 4 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    July 19 Release Notes

    • 4 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    Reporting: Dimension Security Export API Enhancements

    The Get_Dimension_Security_By_Segment APl has been enhanced and a new property has been introduced with this release. You can export only selected members using this property.

    • New Selective property

    Request

    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/ [schemas.xmlsoap.org]" xmlns:ns="http://www.HostAnalytics.com/API/SOAP/StateFree/Common/2009/03/19">

<soapenv:Header/>

<soapenv:Body>

<ns:Get_Dimension_Security_By_Segment>

<!--Optional:-->

<ns:DimensionCode>Company</ns:DimensionCode>

<ns:Model>Financial</ns:Model>

<ns:hasMore>true</ns:hasMore>

<ns:startIndex>0</ns:startIndex>

<!--Optional:-->

<ns:LoginName>skogara@hostanalytics.com</ns:LoginName>

<!--Optional:-->

<ns:Password>Subbu123!</ns:Password>

<!--Optional:-->

<ns:TenantCode>DrillthroughHFJuly27</ns:TenantCode>

<ns:Export>Selective</ns:Export>

</ns:Get_Dimension_Security_By_Segment>

</soapenv:Body>

</soapenv:Envelope>

    Response

    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/ [schemas.xmlsoap.org]" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance [w3.org]" xmlns:xsd="http://www.w3.org/2001/XMLSchema [w3.org]">

<soap:Body>

<Get_Dimension_Security_By_SegmentResponse xmlns="http://www.HostAnalytics.com/API/SOAP/StateFree/Common/2009/03/19">

<Get_Dimension_Security_By_SegmentResult>

<SegmentMemberSecurityInfo>

<UserLogin>skogara@hostanalytics.com</UserLogin>

<SegmentMemberCode>HYD</SegmentMemberCode>

</SegmentMemberSecurityInfo>

<SegmentMemberSecurityInfo>

<UserLogin>zzuser1@ha.com</UserLogin>

<SegmentMemberCode>Company Main</SegmentMemberCode>

</SegmentMemberSecurityInfo>

</Get_Dimension_Security_By_SegmentResult>

<hasMore>false</hasMore>

</Get_Dimension_Security_By_SegmentResponse>

</soap:Body>

</soap:Envelope>

    For example, if you use the Selective property, only the selected members from the hierarchy are displayed in the Dimension Security report as shown in the image.

    If you use All property, leaf and roll up level data is displayed in the Dimension Security report as shown in the image.

    • Enhancement in All property
      • With this release, when you use All property and the Copy Budget Entity Security to Report Security check box is selected, all the Dimension members are displayed if a user is assigned full access in the Approval Role page. The following code shows the API response.
    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<soap:Body>

<Get_Dimension_Security_By_SegmentResponse xmlns="http://www.HostAnalytics.com/API/SOAP/StateFree/Common/2009/03/19">

<Get_Dimension_Security_By_SegmentResult>

<SegmentMemberSecurityInfo>

<UserLogin>skogara@hostanalytics.com</UserLogin>

<SegmentMemberCode>Host Default</SegmentMemberCode>

</SegmentMemberSecurityInfo>

<SegmentMemberSecurityInfo>

<UserLogin>skogara@hostanalytics.com</UserLogin>

<SegmentMemberCode>Company Main</SegmentMemberCode>

</SegmentMemberSecurityInfo>

<SegmentMemberSecurityInfo>

<UserLogin>skogara@hostanalytics.com</UserLogin>

<SegmentMemberCode>Guntur</SegmentMemberCode>

</SegmentMemberSecurityInfo>

<SegmentMemberSecurityInfo>

<UserLogin>skogara@hostanalytics.com</UserLogin>

<SegmentMemberCode>G1</SegmentMemberCode>

</SegmentMemberSecurityInfo>

<SegmentMemberSecurityInfo>

<UserLogin>skogara@hostanalytics.com</UserLogin>

<SegmentMemberCode>G2</SegmentMemberCode>

</SegmentMemberSecurityInfo>

<SegmentMemberSecurityInfo>

<UserLogin>skogara@hostanalytics.com</UserLogin>

<SegmentMemberCode>Vij</SegmentMemberCode>

</SegmentMemberSecurityInfo>

<SegmentMemberSecurityInfo>

<UserLogin>skogara@hostanalytics.com</UserLogin>

<SegmentMemberCode>v1</SegmentMemberCode>

</SegmentMemberSecurityInfo>

<SegmentMemberSecurityInfo>

<UserLogin>skogara@hostanalytics.com</UserLogin>

<SegmentMemberCode>V2</SegmentMemberCode>

</SegmentMemberSecurityInfo>

<SegmentMemberSecurityInfo>

<UserLogin>skogara@hostanalytics.com</UserLogin>

<SegmentMemberCode>Pune</SegmentMemberCode>

</SegmentMemberSecurityInfo>

<SegmentMemberSecurityInfo>

<UserLogin>skogara@hostanalytics.com</UserLogin>

<SegmentMemberCode>P1</SegmentMemberCode>

</SegmentMemberSecurityInfo>

<SegmentMemberSecurityInfo>

<UserLogin>skogara@hostanalytics.com</UserLogin>

<SegmentMemberCode>P2</SegmentMemberCode>

</SegmentMemberSecurityInfo>

<SegmentMemberSecurityInfo>

<UserLogin>skogara@hostanalytics.com</UserLogin>

<SegmentMemberCode>Banglore</SegmentMemberCode>

</SegmentMemberSecurityInfo>

<SegmentMemberSecurityInfo>

<UserLogin>skogara@hostanalytics.com</UserLogin>

<SegmentMemberCode>B1</SegmentMemberCode>

</SegmentMemberSecurityInfo>

<SegmentMemberSecurityInfo>

<UserLogin>skogara@hostanalytics.com</UserLogin>

<SegmentMemberCode>B2</SegmentMemberCode>

</SegmentMemberSecurityInfo>

<SegmentMemberSecurityInfo>

<SegmentMemberCode>HYD</SegmentMemberCode>

<UserLogin>skogara@hostanalytics.com</UserLogin>

</SegmentMemberSecurityInfo>

<SegmentMemberSecurityInfo>

<UserLogin>skogara@hostanalytics.com</UserLogin>

<SegmentMemberCode>1000</SegmentMemberCode>

</SegmentMemberSecurityInfo>

<SegmentMemberSecurityInfo>

<UserLogin>skogara@hostanalytics.com</UserLogin>

<SegmentMemberCode>1010</SegmentMemberCode>

</SegmentMemberSecurityInfo>

</Get_Dimension_Security_By_SegmentResult>

<hasMore>false</hasMore>

</Get_Dimension_Security_By_SegmentResponse>

</soap:Body>

</soap:Envelope>

    Prior to this release, if the user is assigned full access in the Approval Role page, all the Dimension members were not displayed. The following code shows the API response.

    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<soap:Body>

<Get_Dimension_Security_By_SegmentResponse xmlns="http://www.HostAnalytics.com/API/SOAP/StateFree/Common/2009/03/19">

<Get_Dimension_Security_By_SegmentResult/>

<hasMore>false</hasMore>

</Get_Dimension_Security_By_SegmentResponse>

</soap:Body>

</soap:Envelope>

    • When you use All property and the user has access to members from the Approval Role and Dimension Security page all the records are displayed in the Dimension Security report. Prior to this release, duplicate records were displayed if All property was used.

    • With this release, inactive and locked user details are not displayed in the Dimension Security report. Now locked and inactive user details are restricted.

    • Now if the user has access to Main root level, the Dimension Security report displays root members. Prior to this release, root members were not displayed in the response.

    Reporting: New Report Security is Enabled for All New Customers

    With this release, the new Report Security functionality is now enabled by default for all new applications that are created after the July 19 release.

    Platform: Enhancement in NetSuite Connect DLR

    With this release, the following functionality is enabled for the NetSuite Connect DLR in the Define Overall Rule Settings page:

    • Allow Property Change check box: Select this check box while loading the segment hierarchies to allow property changes (such as Name, Currency, and so on) for existing members.
    Note:
    This functionality is applicable only for the Parent Child Segment Hierarchies load.

    Prior to this release, the Allow Property Change check box was disabled for the NetSuite Connect Segment Hierarchies load.

    The Level Based loads and Allow Property Change functionality for Level Based Segment Hierarchies loads will be enabled with the Summer 19 release.

    Modeling: No New Add-In

    There is no new add-in this release and no need to upgrade your existing client software.

    See Where to Download SpotlightXL and Version Information for information.

    Modeling: Ability to User Filters in ESM to ESM Maps

    Modeling supports copying data from one External Source Model (ESM) to another External Source Model. Just as you can copy data from an External Source Model to a Master or Analytic model using an ESM map, you can use the same method to copy data from one ESM to another.

    With this release, we've enhanced the way data is cleared when filters are used, which improves performance. To copy data from the source to the target ESM, a Calculation is executed to run the External Source Map. When the map is run, all data in the target ESM is deleted before the data transfer from the Source Model is done, if there are no filters defined in the map. Now, if there are filters defined in the map, the data in the target ESM will be deleted based on the filters and the source data will also be filtered based on the filters defined.

    For example, using the example ESM to ESM map below, a filter is defined on the Sales Segment field and Enterprise is the value. When this map is executed from a Calculation, the map will only move the Enterprise data from source ESM to target ESM. Additionally, the Enterprise data only in the target ESM will be cleared before the data is moved from source to target.

    For detailed information on the specific steps to create an ESM to ESM map and run a Calculation, see the Transferring Data from One External Source Model to Another External Source Model topic.

    Was this article helpful?
    What's Next

      Planful. 150 Spear Street, Suite 1850, San Francisco, CA 94105

    • Copyright © 2024 Planful. All Rights Reserved.

    Terms of Use - Privacy Policy