How to create a Lawson Business Intelligence (LBI) Report Schedule

, ,

You may have a report in LBI that you want to create historical instances of as well as refresh data from time to time. Today we are going to go over how to do this in Reporting Services Admin.

 

  1. Login into LBI as an admin user and go to Reporting Services Administration
  2. Go to Maintain Reports and open the report via the [Details] link next to the report name.
  3. In the report under Scheduling, select New Schedule
  4. Under Run Date and Time fill in the:
    1. Name (schedule name)
    2. Instance Name (name of generated report), you must manually re-schedule if you want to include specific unique information in the name like date.
    3. Description
  5. Under Time and Frequency:
    1. Set the Scheduled Run Time (time of day)
    2. Time and Frequency
      1. Schedule for days in a Week – This will run for every day in the week you select regardless of date.
      2. Schedule for days in a Month – This will run the day you select in a month. Please note that there are specific check boxes for First and Last day in the month. If a month does not have a day like the 30th or 31st, it will skip that month.
    3. Effective Date Period
      1. Effective start date: This date must be set after current date and time.
      2. Expiration date: The report will no longer run this schedule after this date and time.
  6. The remaining Schedule Options should typically mirror the report options. Any customizations will not change the base report.

This type of work is typically done by a Lawson technical and or functional resource depending on the type of reports and their complexity. Organizations often hire a Lawson consultant team who offer managed services at a fixed monthly rate. These Lawson teams have a wider range of expertise and knowledge and are ideal for larger organizations but also are great for smaller ones that don’t need a dedicated Lawson employee on-site. Nogalis does offer this as a service so feel free to reach out to us via our contact page.

How to Verify a user is set as a Ming.le user

, ,

To verify a user is set as a Ming.le user, we will use the IsMingleUser column as an example to complete the steps below:

  1. Login and access the GEN data area
  2. Navigate to the Actor List
  3. Click Options (In the Web UI you will need to click the ellipsis first)
  4. Select Personalize
    1. If this is the first personalization you will need to click create
    2. If you are updating an existing personalization you will need to click update
  5. Click the + button > Add field
  6. Click the Search button
  7. Type ‘ism’ in the search field and hit enter
  8. Select IsMingleUser from the list
  9. Click OK
    1. If you wish to change the default label for the column, update the label box
  10. Check the box next to Updateable
    1. Depending on your LMK version, you may need to add the field and then edit it to check the box next to “Allow data to be updated in the list”
  11. Click OK

You are then returned to the actor list which will update and the IsMingleUser column will be added to the Actor List screen.

 

Note:

Other columns that you may want to add to assist with user provisioning include:

 

IsActorDisabled – make updateable

IsAckBodReq – make updateable

MingleId – make updateable

IsActorIFSDisabled

AccountLockout.IsAccountDisabled

 

Beginning with versions 2022.03.00..632 (MT) and 11.0.51.0.6489 (ST/OP) the following fields have been added as updateable to the default Actor List:

 

IsMingleUser

IsActorDisabled

IsActorIFSDisabled

IsAckBodReq

MingleId

How to find a Lawson user ID from an HR11 Employee ID

, ,

Some Lawson Security systems are setup with a form of the user ID being a combination of the last name with middle initials / first name initials.

Something like DoeJ for John Doe. Often users get their names updated due to a marriage or divorce and their user ID never gets updated along with their last name.

  1. To find the user by employee number, we need to first go to HR11 and find the user by their new last name to uncover their Employee ID.
  2. For this example, let’s say we search John Doe and it returns an employee ID of 264
  3. Now open Lawson Security Administrator and go to User Management >> Manage Identities
  4. Once in Manage Identities under “Services”, select the employee identity service, ours is named TEST10_EMPLOYEE:
  5. Select employee = <employee ID> and click Add Criteria
  6. Once the criteria is added, Execute Query
  7. You’ll be put to the results tab and if that user exists in Lawson security, it will show as so:

This type of work is typically done by a Lawson technical resource with a Security Administrator background. Organizations often hire a Lawson consultant team who offer managed services at a fixed monthly rate. These Lawson teams have a wider range of expertise and knowledge and are ideal for larger organizations but also are great for smaller ones that don’t need a dedicated Lawson employee on-site. Nogalis does offer this as a service so feel free to reach out to us via our contact page.

How to Convert a Non Ming.le user to a Ming.le user

, ,

One-time setup prerequisite
Before making any changes to users, if you do not already see the fields listed below in your Actor List in Landmark (LMK), please review KB 2017273 How to personalize the Actor List in Landmark and add the following fields and make them updateable:
IsMingleUser
IsActorDisabled
MingleID

The above attributes are included in the default view of the Actor List beginning with 2022.03 and 11.0.51

User Conversion Process

Lawson System Foundation (LSF) – skip this part of the process if your system does not include LSF
1. Login to Lawson Security Administrator (LSA)
2. Search for the user to be converted
3. In the search results, right click on the user and select edit RM information
4. Ensure the isDisabled field is set to No
a. If it is set to Yes, change it to No and save the change
5. Repeat steps 2-4 for each user that needs to be converted

Landmark
1. Login to Landmark
2. Navigate to the GEN data area – if you have a bookmark use that, if not use the steps below
a. Switch to the Administration Console role
b. Click Other
c. Click Application and System Links
d. In the new tab that opens, click User Management under Security Administration in the lower left corner of the screen
3. Click Actor in the left side menu
4. Search the Actor List for the user to be converted
5. Open the user from the Actor List
6. Ensure the actor has a valid unique email address on the contact tab
7. Save any changes made
8. Return to the Actor List – use the browser back button
9. Ensure the following about the user:
a. Actor Disabled is set to No
b. Mingle User is set to Yes
c. Ming.le ID is completed
-Update any information above that is not correct
-Ensure that the Ming.le ID is populated before setting Mingle User to yes
10. Save any changes made using the save button at the top of the list or under the actions menu

The user is now set up as a Ming.le user and has all required fields for updates to be sent between Landmark and Ming.le.
You can verify this by checking the following:
1. The user(s) exist in Ming.le User Management
2. The IFS ION Person ID in Ming.le matches the SSOP or SSOPv2 identity value in Landmark
3. The IFS ION Person ID in Ming.le matches the SSOP identity value in LSA
a. Updates to LSF are processed every 30 minutes on the hour and half hour when the IONREAD job runs. If you want to see the change before the job runs login to LID and run the readinbox command

Lawson MHC – An Error occurred while printing

, ,

Scenario: You have Lawson invoices or orders that get moved over to MHC.

When you print them from MHC, the print queue you have setup produces PDF.

 

An error occurred while printing

 

Make sure you go into the folder where the PDFs are produced and delete any old or existing ones.

 

This all depends on how you’ve setup your print queues. Good luck!

Getting started with Spreadsheet Designer

, ,

Here is a brief guide to get yourself set up with Spreadsheet Designer (ISD).

  1. Ability to comment out rows and worksheet/s enhancement is available in ISD 10.0.16.245.
  2. Click the Infor Button > Settings

The feature is disabled by initial install/upgrade. Check the Comments>Enable checkbox to turn on comments.

 

 

  1. Using Row Comment
    • For row comment/s, insert “//<space>” or “// ”on first column of the row.
    • Click Upload/Upload Sheet Range/Upload All

 

** For Batch Upload, check Upload in Batch Mode in Settings, then repeat steps 4.1 and 4.2

 

 

  1. Using Worksheet Comment
    • For Worksheet comment, insert “/*<space>” or “/* ”on first cell of the Worksheet (cell A1).

Or

  • Click Upload or Upload All

** For Batch Upload, check Upload in Batch Mode in Settings, then repeat steps 5.1 and 5.2

 

Lawson ISS – Using an ISS Sync to remove roles assigned to users

, ,

In Lawson ISS, you may come across one or both of the two scenarios below:

  1. I removed a role from a number of users in Lawson System Foundation (LSF) and want to use an Infor Security Services (ISS) sync to remove these same roles from Landmark (LMK).

or

  1. I removed a role from a number of users in Landmark (LMK) and want to use an Infor Security Services (ISS) sync to remove these same roles from Lawson System Foundation (LSF).

 

There is a resolution for both of these scenarios:

A full ISS sync does not have the ability to remove roles from users. However, you can run a list-based sync via an ssoconfig command to remove the roles in the other system.

 

There is a flag that can be included in the list-based sync file that allows for roles to be overwritten in the system that is being updated called the mergeActorRoles flag. When this flag is not included in the xml file to be used, or is set to true, the roles from the source system (the one you are NOT updating) that are not found in the other system will be appended to the roles currently assigned. When this flag is set to false, mergeActorRoles=false, the roles assigned in the system that is being updated will be overwritten to match those in the source system, hence removing roles if necessary.

 

A list-based file template is delivered with each upgrade to ISS, you will use this file as a base for your work. The location of the file is:

 

GENDIR\system\provisioning\metadata\backgroundSyncTemplate.xml

Create a copy of the file and edit the copy, ensure the following are set:

 

defAction is set to update the system where the roles have NOT already been removed options:  update_remote or update_local

mergeActorRoles is set to false

IMPORTANT: The local and remote sections shown in the example below MUST be included since the users already exist in bot LSF and Landmark. These areas would contain each user to be updated.

Example of a completed list-based sync file that will update roles in LMK for existing users test1 and test2 to match roles in LSF:

Once you have the file the way you need it, you need to run the ssoconfig command for the list based sync.

The syntax for that is as follows and there is no ssoconfig password required for this process/command syntax:

 

ssoconfig -S sync_file_with_fullDirectoryPath

 

Example command for Windows customers:  ssoconfig -S D:\LSFPROD\gen\system\provisioning\metadata\FileNameOfBackgroundSyncTemplate.xml

Example command for Unix or IBM i customers: ssoconfig -S /LSFPROD/gen/system/provisioning/metadata/FileNameOfBackgroundSyncTemplate.xml

 

NOTE: In the above examples, if you placed the xml file for this process in another directory, simply replace the full path to the location of your xml file.