Grow BI connects to Kinetic Pilot for early data validation.
Kinetic Public Cloud customers can connect Grow BI to their pilot environment, gaining early visibility into ERP data before production. Embedded visuals in standard dashboards reveal anomalies without extra effort.
For example, a bar chart shows Orders by Region, but one entry “07/03/2025” exposes a bad data entry—helping customers correct issues before go-live.
Adding the Access Scope
Access scopes limit what areas of Kinetic a user can launch and run. Your Cloud or On-Premise environment needs an access scope that only has the services and methods the integrated user account needs to connect Kinetic with Grow. If the GrowKinetic access scope is not yet available in your environment, follow these steps to create it.
Log into your Pilot or live Kinetic instance (depending on which you are wanting to connect).
Launch Access Scope Maintenance. Go to System Setup > Security Maintenance > Access Scope.
Select Add New.
Enter an Access Scope ID, such as GrowKinetic.
Enter a Description for the access scope.
Now add the services Kinetic needs to integrate with Grow. Expand the Nav Tree and select the Service List node.
Go to the Service List grid and select Add New.
Find and select the ICE.BO.UserFile service. This service handles the Kinetic user accounts.
Now add the method for this UserFile service. Go to the Methods grid and select Add New.
Find and select the GetCompanyListForUser method. This method pulls in the companies that each user account can access.
Return to the Service List grid and select Add New.
Find and select the ICE.Lib.SessionMod service. This services runs the each Kinetic session.
Add the method for this SessionMod service. Make sure you select this service in the Service List, then go to the Methods grid. Select Add New.
Find and select the GetPatchLevelApp service. This service checks the current Kinetic version.
Save
the GrowKinetic access scope.