Example:
Sales rep Jake Klister (user ID 82489) was originally set up under Demand Construction (company ID 2435) and his admin requested Enerflo to move him to a different org, Demand (4273). After using the user migration tool to transfer the rep along with his deals to the new org, the rep tried to submit a design request and got the following error:
"There was an error with your request. Solo Error: User's company_id doesn't match logIn/input company_id or any of it's children company_id. Please check the inputted user information and try again."
Also, when you went to his deals and clicked "deal details" to look at the sales rep info, there was not an email showing under his name.
/span>
How to avoid this error:
Go to admin.enerflo.io > users and search for the rep's name.
Go to their profile and to the section "Org Authorization." Ensure that the org the rep has access to matches the company that the rep is set up under. If not, update the org and the error should go away. In this example, Demand Construction was still showing as the only org the rep had access to. After, updating the org to Demand, the error went away.
/span>
If the org the rep is transferred to is using Solo, it is important to double check that the rep's solo design requests go to the correct solo account. Some installers set up Solo child accounts for their orgs while other installers will have all their sales orgs use their main Solo account. As you can see, Demand's solo account is Demand Domestic and the rep's request was successfully sent to that account. If the request isn't sent to the correct Solo account, you might need to check the account that has been selected in the Solo plug- in and that the user has been set up under the correct solo account.
/span>
/span>