Follow the steps below to learn how to reorganize or modify your columns in (Lawson Business Intelligence) LBI Maintain Reports.
Problem:
You’re an admin for Lawson LBI but you want to reorganize the Maintain Reports columns like the ones shown below:
Solution:
There is a simple way to do this. Just follow these steps.
- First, log in to LBI and open your Report Administrator:
- Next, go to My Reports on the side bar:
- Make sure “ALL” is selected under the left column under Report Lists
- Click “Edit List” on the top right and reorganize the columns, then click save.
Go back to Maintain Reports and you should see your new columns!
Each Process Automation user has an Inbasket that is accessible through Infor Smart Office. Your Inbasket contains tasks that have been assigned to you, as well as the user’s information.
Problem:
Users’ name changed but is not reflected in Inbasket. (See screen shot below for example)
Resolution:
In Infor Security Services (ISS), the Preferred Given Name is listed as “Linda”. The value can be updated in this section if the person has changed their name (or if for some reason the name is wrong or misspelled).
Once you edit the “Given Name” field, save your changes. The name displayed should now be the correct one.
User Excel Add-ins Issue Summary:
User can no longer query Lawson data and ruled out that it is NOT a Lawson add-ins version issue. Follow the steps below to see if this resolution helps.
- First, we had to enable add-ins from disabled items, File >> Excel Options >> Add-ins >> Manage “Disable Items” >> Go, then select and enable.
- Then in Excel Options >> Add-ins >> Manage “Com Add-ins”, enable Lawson MOA (Acrobat PDFMaker in the past has caused issues, so disable if it does, we left it enabled and it worked)
- This initially fixed the issue, everything worked.
However, when the user restarted Excel app, they had to re-add it in COM Add-ins every time. If this happens to you, go to step 4, else you’re done!
- Optional if having issues after step 3: Running Excel as Administrator fixed the issue in step 3, but since it’s now under the “admin account”, accessing add-ins scripts prompted share folder permission issues from Excel:
What we tried: adding folder permissions for the user to C:\Program Files(x86)\Lawson Software and \Microsoft Office folder permissions. This did NOT work.
- Optional if having issues after step 3: Last thing that resolved the issue was updating the registry manually.
- Open REGEDIT
- Go to HKEY_CURRENT_USER\Software\Microsoft\Office \Excel\Addins\<YourAddinName> (In our case, it was named Lawson MOA Add-ins)
- Select Lawson MOA Add-ins, on the right of regedit select “LoadBehavior”
- Set the LoadBehavior value to 3 (Load at Startup)
- Other values include 0 = Unloaded, 1 = Loaded Manually, 2 = Load on demand
After step 5, add-ins tab appeared when the user opened Excel normally, everything worked from there on out.
If you need to change the account that owns smart notes and/or the notifications, you can execute a mass change using the database. Open your LBI database server using a database editing tool. Then, run a query against your Smart Notes db (often called “LawsonSN”).
First, get the IDs for your current owner and the new owner from ENPUSERMAP. You should be able to search on the username and grab the numeric id from there.
Next, make an update to the ENPBATREE. Set the entry owner to the new id where it is set to the current id. The query will look something like this (in this case, current owner is id 5 and new owner is id 3):
update ENPBATREE set ENTRYOWNER = 3 where ENTRYOWNER = 5
That’s it! Now, when you log into Smart Notes as the new owner, you will see all the notifications!
Follow these steps to update a user’s Database and User Roles via Infor Lawson Cloudsuite:
- Login to your concierge account and go to Cloudsuite app (this assumes you have access to this else open a ticket with Infor).
- Create a Service Request
- Select Deployment and Request Type: SQL Manage User
- Select Database Server and in the drop down select Modify User
All done! Validate with the user. If this is something you’re need assistance managing, Nogalis offers a team of Lawson specialists within a single MSP services contract for customers. Let us know if we can assist you today.
PROBLEM
Users may encounter a receiving issue when processing a purchase order where the system prevents reprinting the ticket and does not allow backing out to PO33 to reprint. When attempting to release the item during receiving, the system displays the error message: “Line one has outstanding buyer message.” This issue typically occurs when a buyer message was entered on the purchase order line and has not yet been acknowledged or released.
RESOLUTION
To resolve this issue, navigate to PO52.1 and release the buyer message associated with the affected line.
Ensure you are working in the correct Company (10) and locate the appropriate Receiver (7273187).
Once the buyer message for Line 1 is released, return to PO30.1 and proceed with receiving and printing as expected.
The user does not appear on the Soft Deleted Users page until being deleted from the Users page.
If Soft Delete is the user deletion method, to delete a user:
While logged in as a user with a UserAdmin role, click the profile icon in the top right corner of the screen to access the profile panel.
Click User Management on the profile panel.
Click Soft Deleted Users under Manage.
On the Soft Deleted Users screen, enter the name of the user to be deleted in the search box on the right and press Enter.
Click the Soft Deleted Users table and select the check box next to the name of the user to be deleted.
Select Action > Delete.
Click on the refresh button to see if the sync completes. It is complete when the + is not grayed out. Also, you will see the manual execution and status of success.
To troubleshoot, highlight a collision one and scroll down to the bottom of the page to see the errors.
Validate:
Is user in InforOS?
https://chromewebstore.google.com/detail/saml-tracer/mpdajninpobndbfcldcmbpnnbhibjmch?hl=en
Export the AD User-Get-ADUser username -Properties * | Select * > username.txt to check AD to make sure UPN doesn’t have any weird characters in it.
An Error Occurred:
In INFOR OS, Check Soft deleted users, hard delete and sync
Infor OS Mingle Logs on-prem Logs:
Other notes: Export the AD user to check AD for unique characters that are causing the UPN to not match up with Infor OS, also check Infor OS for those same characters.
Get-ADUser username -Properties * | Select * > username.txt
SAML Tracer
In order to add items (or users manually in Infor OS), AD Params would need to be “manual” (not All Users) this is in OS Security User Management



































