Welcome to Part 4 of this 5-part blog where I share my findings and tips on how to configure the integration between Netsuite and PBCS using the in-built adapter.
Part 1 - User based vs Token Based Authentication
Part 2 - Tips on setting up your Saved Search in Netsuite
Part 3 - Tips on setting up Data Management in Planning Cloud
**Part 4 - How to set up Drill through from Planning Cloud to Netsuite**
Part 5 - How to give your end users access to run the integrations
In the Drill URL box, enter the following:
https://AccountNumber.app.netsuite.com/app/common/search/searchresults.nl?
Your account number can be found in the URL of your Netsuite environment
e.g.
Production: https://1234567.app.netsuite.com/app/center/card.nl?sc=-46&whence=
Sandbox: https://1234567_SB1.app.netsuite.com/app/center/card.nl?sc=-46&whence=
Target Application
2. Go to Target Application and select your Planning Application,
check the boxes for the dimensions you want to appear in the drill region.
3. Under Application Options, set Drill through to Yes
Import Format
4. Go to your Import Format for the integration
The drill through takes the user to the saved search which is used
as the source of the integration; therefore, we need to reduce the scope of the
saved search to that of the cell which is drilled down on.
To do this, you must have columns in your saved search for the Internal ID of Account, Period and optionally Entity/Subsidiary (See part 2 for
more information on setting up your Saved Search)
You then add Attribute type rows to your Import format for Account, Period and optionally Subsidiary and map the Internal ID column of these segments to the Attribute rows.
Now we can reference these attributes in the URL that Data
Management passes to Netsuite in the Drill-through process.
5. In the drill URL box, enter the URL in a similar format to below:
searchtype=Transaction&searchid=164493&Transaction_ACCOUNT=$ATTR1$&Transaction_POSTINGPERIOD=$ATTR2$&Transaction_SUBSIDIARY=$ATTR3$&Transaction_POSTING=T
Let’s break this down:
searchtype=Transaction&searchid=164493 : This number is
the ID of the saved search
Transaction_ACCOUNT=$ATTR1$ : Account is mapped to Attribute 1 in
the import format
Transaction_POSTINGPERIOD=$ATTR2$ : Period ID is mapped to Attribute
2
Transaction_SUBSIDIARY=$ATTR3$ : Subsidiary is mapped to Attribute
3
Transaction_POSTING=T : Sets Posting = True
Data Load Rule
6. Go to your Data Load Rule > Target Options, check that the Drill Region is set to Yes.
That's all for Part 4, stay tuned for Part 5 - How to give your end users access to run the integrations.
Thanks for reading :)
Ciao for now.
No comments:
Post a Comment