Issues with MA References in LAPMgr

Owned by Robert Adach, created
Feb 24, 2022
3 min read

There are 2 issues that may occur when dealing with references in LAPMgr.

  1. One or more references will not import

  2. When accessing imported references, the system crashes

One or more references will not import

This issue is generally caused by reference responses containing one or more “non-printable”/non-ASCII characters.

  1. Open SSMS and connect to the 192.168.100.160 server

  2. Run the following script to remove all non-printable characters.

  3. EXEC [dev_CleanRefsToImport]

  4. When the stored procedure has completed, the system will then list all of the fields associated with all of the references awaiting import

  5. Review the list and look for:

    1. “FALSE” values in the “Value OK” column

    2. any date field with a date in the future

  6. You must address all of the “FALSE” values before the reference can be imported.

  7. You can use the code below to update the values replacing the <FormDataID> with the value for the field you are correcting

  8. UPDATE tblFormData SET DataValue = <Corrected Data value> WHERE FormDataID = <FormDataID>

Correcting this issue can be complicated if the team is using the “Import All” button on the Manage References page vs the Import one, as the system does not import references in any specific order. It is suggested that the team use the Import One button until all but the problem reference(s) are left

When accessing imported references, the system crashes

This issue is generally caused by one of two issues:

  1. There are multiple supervisor references and one of them has three separate supervisory periods, and all of the others do not.

  2. One or more of the dates on the a reference are incorrect (the start date of a period is after the end date, the date entered is incorrect (3/31/1022 instead of 3/1/2022)

To begin

  1. Open SSMS and connect to the 192.168.100.160\LAP database

  2. Run the following script replacing <Review Number> with the Application Review number with the issue

EXEC dev_CheckImportedSupRefs @ReviewNum = <Review Number>

If the column “[3 Supervision period issue]” has a yes value:

  1. Locate the reference which has 3 supervision periods

  2. Run the following script replacing <Reference ID> with the MAReferenceID you have documented

  4. Copy and paste the output of the above script as an internal comment in the Jira ticket.

  5. Run the following script to backup the data, and consolidate the supervisiory periods

  7. Once the process has completed, let MSERV know that they can continue processing the application and will need to reopen the ticket when all processing is done to restore the data.

  8. To restore the data run the following script

  10. You can run the stored procedure without any variable declarations and usage instructions will popup

If any other column has a yes value:

  1. Look for any column which has a Yes value

  2. Determine the correct value, if you are unable to determine it yourself, let MSERV know what is wrong and ask them to identify the proper date

    1. Example: In reviewing the references for review number 1234, we have found that the first supervision ending date for the reference is an invalid date. The date entered is 2/1/2012 and is before the first supervision start date. Please provide the correct date so we may update the system

  3. To correct the value make sure you have a) The MAReferenceID value, the ColumnName, the correct value, the update and run the following script.

    1. It is recommended that you only run one update at a time

  5. After completing all necessary updates rerun the stored procedure executed in step 3

  6. If all values are correct, the open LAPMgr and log in

  7. Load the application that has the issue with the reference(s)

  8. Click on References/Supervision tab

  9. At the top of the form you will see a grid of references

  10. Beginning with the second reference on the list (do not be concerned with the reference type), click on each reference until you have clicked on the last one listed. Make sure you wait for the data to refresh on the screen before moving to the next reference.

  11. Repeat step 13 but work from the bottom of the list to the top.

  12. If you are able to complete steps 13 & 14 without the system crashing you have resolved the issue.

 Related articles