Explanation:  When a user is assigned to an account with a role that does not have the "View Devices" permission and when the System configuration option "Enforce device management permissions across accounts" is enabled in the FNO for "End-User Portal Setup", and the user accesses the device in the end user portal, this error message is displayed. Use Case 1: [Accessing the device in the End User portal for two different accounts linked to the same user when the system configuration is enabled] 1. Customer User details. Customer Username Account Id Role name Permission Device ID shreyashs1073@gmail.com TestAc-3 INF-portal admin user role has 'View Devices' permission TestSA01 shreyashs1073@gmail.com TestAc-4 INF-portal user role doesn't have 'View Devices' permission TestSA02 Reference images :  2. In the FNO -> System Configuration -> End-User Portal Setup -> Select the checkbox for this option "Enforce device management permissions across accounts". This controls the capabilities available on the Device Details page. When a user with multiple accounts select a device, their permissions to view or manage devices, will be applied based on the ownership of the device within that selected account.   3. Then, in the end user portal device page, the user can access 'TestSA01' device without any issues. But, when the same user tries to click on 'TestSA02' device which is linked to 'TestAc-4' account id, encounters an error message- "Insufficient permissions to view the device within the account."     Use Case 2: [Accessing the device in the End User portal for two different accounts linked to the same user when the system configuration is disabled] 1. When the system configuration "Enforce device management permissions across accounts" is disabled, then the same user with the account 'TestAc-4' can access the 2nd device 'TestSA02' without any issues.    ... View more

Description In the FNO there are customer users, producer users, partner users and self register users. For example, if the producer user would like to become a customer user or any other user, users can update their existing producer user account to customer user account including the associated roles. Use Case Before converting an existing user to a different user type, ensure that the customer type account ID or any other account ID exists in FNO. Hint: In the SOAP request, keep the user details as it is. Just update the Account ID and Roles with REPLACE(OperationType) in the 'updateUser' request. Users can find the latest version of the 'UserAcctHierarchyService' from the https://<siteID>.flexnetoperations.com/flexnet/services, where <siteID> is the site ID for your organization, supplied by Revenera. (for example, https://flex1234-uat.flexnetoperations.com/flexnet/services ) In the API tool such as SOAP UI or Postman, load the WSDL endpoint URL. The UAT URL format for version 2 is: https://tenantID-uat.flexnetoperations.com/flexnet/services/v2/UserAcctHierarchyService?wsdl, where tenantID follows the format flexNNNN (for example, flex1234). Use Case 1: Move Producer user to Customer user 1. Primarily, the user 'test03@gmail.com' was seen under "Producer Users" tab. Before execution:   2. Webservice updateUser request to update the user type from one to another:   3. After executing the 'updateUser' request, 'test03@gmail.com' seen under "Customer User".  Result: The "Producer User" has been converted to "Customer User". Sample Request: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:v2.webservices.operations.flexnet.com"> <soapenv:Header/> <soapenv:Body> <urn:updateUserRequest> <urn:userData> <urn:user> <urn:userName>test03@gmail.com</urn:userName> <urn:primaryKeys> <urn:firstName>Test03</urn:firstName> <urn:lastName>User03</urn:lastName> <urn:emailAddress>test03@gmail.com</urn:emailAddress> </urn:primaryKeys> </urn:user> <urn:acctRolesList> <urn:acctRoles> <urn:account> <urn:primaryKeys> <urn:id>CUST100</urn:id><!--Account id:--> </urn:primaryKeys> </urn:account> <urn:roles> <urn:role> <urn:primaryKeys> <urn:name>SuperPortal Role</urn:name><!--Role name 1:--> </urn:primaryKeys> </urn:role> <urn:role> <urn:primaryKeys> <urn:name>Software Engineer I</urn:name><!--Role name 2:--> </urn:primaryKeys> </urn:role> </urn:roles> </urn:acctRoles> <urn:opType>REPLACE</urn:opType><!--OperationType:--> </urn:acctRolesList> </urn:userData> </urn:updateUserRequest> </soapenv:Body> </soapenv:Envelope>   Hence, we can use this method to move user from one type to another. ... View more

Points to remember: 1. Under the System > System Configuration > End-User Portal Setup > Select 'Entitlements Page' > 'Hide Split' option must be unchecked. 2. Ensure that 'Split Line Items or Bulk Entitlements' permission is selected for the user's role who is performing the split operation. 3. The split operation can be performed on the end user portal, when the entitlement is linked to the distributor(Channel Partner Account) without the information of end customer account[UNKNOWN_ORG_UNIT (Information Not Available)]. 4. One of the partner tiers (either the partner account or one of its sub-accounts) of an entitlement must be set as Current Owner before an entitlement can be split. 5. A new related customer account can be created while performing the split entitlement. To assign entitlement for newly created Related Customer Account: Click on 'Search Account' icon that is present next to the 'Target Account' > Hover over the Action menu > The option to create a new related customer account is available and the account can be created > After creating this account, select this account to split. 6. For the Distribution Type/Tier Name: Distributor, A new related partner account cannot be created and this action will fail with the error message "Cannot split to tier Distributor; this tier has already been defined on the entitlement."   Instructions: Step 1: Click on create option under the Entitlements menu in the Producer portal.  Step 2: Link the entitlement to any Channel Partner account(Distributor) and click on 'Save'. Step 3: Add a new line item for the entitlement and then click on 'Save & Deploy' button. Step 4: Log in to the end user portal with user credentials. Step 5: Under 'Activations & Entitlements' menu, click on 'List Entitlements' and search for the Entitlement-id/Activation-id that require splitting. Step 6: Select the check box, hover over the 'Action' button and click on 'Split' option. Step 7: Enter the value for 'Split Amount'. Click on search icon, select the 'Target Account' value and 'Save' it.(Note: User can add the new customer account and assign split amount)  Step 8: Next, click the 'Split' button before clicking 'Ok'.  Step 9: The selected line item will be split.    ... View more