Tips to Deploy Microsoft Dynamics SL Web Apps for Existing Dynamics Business Portal Users

Solomon Cloud Solutions brings you tips to deploy Microsoft Dynamics SL Web Apps for existing Microsoft Dynamics Business Portal users more efficiently.

These instructions are for use with Microsoft Dynamics SL Web Apps 2015 CU1 release.
​
Microsoft Dynamics SL 2015 CU1 Web Apps give you the ability to migrate your existing BP users into Web Apps users. Use this set of scripts found in the Web Apps deployment package:

Business Portal to Web Apps Data Migration
Use the data migration scripts to create Microsoft Dynamics SL user IDs for the Business Portal (BP) Project users who do not already have a unique SL user ID, to link BP Project users who have existing SL user IDs, and to populate the SL user ID in Employee and Resource Maintenance for BP Project users and SL user IDs that already match. 

          1. Log in to SQL Server Management Studio as a SQL administrator. 
          2. Create backups of all Microsoft Dynamics SL system and application databases that were previously integrated to Business Portal. 
          3. Open the BPProjectEmployee folder in the Web Apps installation package. 

          4. Configure SQL Server Management Studio so that the query results appear in a grid.(Tools | Options | Query Results | Default destination for results = Results to grids)
          5. Run the BPProjectEmployee2.01_Sys.sql script against each system database.  

          6. Run the BPProjectEmployee2.01_App.sql script against the first application database. 

Note: If you need help from technical support during this process, submit the complete results from this script with your support case.

                    a.) Copy the results in the Recommended Statement column, and paste them into a new query.
                    b.) Review the statements for accuracy and for any changes that you need to make, such as the following:
                             - Changing the name of the BPPROJECTUSER group
                             - Removing an employee that is no longer employed
                             - Removing potential SL user ID duplicates, because Web Apps does not support multiple SL user IDs linked to the same Windows domain user
                             - Removing potential Project Employee duplicates, because Web Apps does not support multiple Project Employees linked to the same SL user ID
                    c.) Run the statements against the same application database.
                    d.) Repeat this step for each Microsoft Dynamics SL application database. 


          7. Validate the results as follows on the application database(s): 

--View the new users who are added by the data migration:
select vs_UserRec.UserID, vs_UserRec.UserName, vs_UserRec.WindowsUserAcct, vs_UserGrp.GroupId, PJEMPLOY.employee, PJEMPLOY.emp_name
from vs_UserRec (nolock)
join vs_UserGrp (nolock) on vs_UserGrp.UserId = vs_UserRec.Userid
join PJEMPLOY (nolock) on PJEMPLOY.user_id = vs_UserRec.Userid
Where GroupID = 'BPPROJECTUSER'
--View all user, group, project employee relationships:
select vs_UserRec.UserID, vs_UserRec.UserName, vs_UserRec.WindowsUserAcct, vs_UserGrp.GroupId, PJEMPLOY.employee, PJEMPLOY.emp_name
from vs_UserRec (nolock)
join vs_UserGrp (nolock) on vs_UserGrp.UserId = vs_UserRec.Userid
join PJEMPLOY (nolock) on PJEMPLOY.user_id = vs_UserRec.Userid
--View the new relationship to the project employee added by the data migration:
select PJEMPLOY.lupd_user, PJEMPLOY.employee, PJEMPLOY.emp_name, PJEMPLOY.user_id
from PJEMPLOY (nolock) where PJEMPLOY.user_id <> ''
--Locate duplicates (you must resolve these duplicates before you continue):
select p1.lupd_user, p1.employee, p1.emp_name, p1.user_id
from PJEMPLOY (nolock) p1
join PJEMPLOY (nolock) p2 on p2.user_id = p1.user_id and p2.user_id <> '' and p2.emp_name <> p1.emp_name

---

​The script creates a list of the users that already exist in BP and how each user is set up. This gives you the opportunity to make business decisions about which users you want to carry forward into Web Apps and exactly what access they need to fulfill their job responsibilities. After initially running the script and reviewing the results you can meet with your customer to make the final decisions about which users need web apps access and what the access rights will look like. Based on these decisions you can make changes to the final set of scripts you will run so the users will have web apps rights set appropriately.
 
Don’t have a web apps developer on staff or your staff is already overworked? Contact us at [email protected] to see how we can help.

---

Solomon Cloud Solutions is a software publisher and consulting organization that provides development and consulting services to partners. Solomon Cloud Solutions was formed specifically to develop a complete cloud platform to accelerate development and deployment of their cloud based business solutions across their family of companies and their business partners. The Solomon Cloud Solutions companies operate under the brand names of Six Disciplines - publisher of performance management software, methodology and coaching and Beyond Software - publisher of project accounting software and are owned by Gary Harpst, Vernon Strong and Jack Ridge.