Retreiving RM Id via Process Flow

Hi Chad Dirst,

Wow. The RM lookup is quite slow, so I'm not surprised. There may be some other options, but they could vary based on what you are doing. Can you describe briefly what your flow does? Why does it need to look up the RM records every time? What is your primary data source (file, SQL, S3 Query, etc)?

If your primary data source is a SQL query, then maybe you could create a custom table with Company/Employee/RMID and do an initial load with your existing values. Then join that custom table to your source query, then only do the RMID lookup (and insert into your custom table) if a value isn't found.

If you are getting a source file from elsewhere, could you possibly do something similar to the above and have the source system include the RM info in the file?

I'm just throwing out some ideas. This is a challenging problem.

We utilize Infor T&E SaaS solution.  Lawson delivered a connector which is a series of flow to interface to the Infor T&E (XM) system.  The root issue is the flows send full data files each time it is run.  In addition, our uses wanted to customize the flows to send the RM Id as the XM Login field.  Lawson does not deliver that as an alternative. 

I understand my alternatives to solve the problem (do not send full files or store the RM Id in a custom table/user field).  I just wanted to check if there were any recommendations on configuration properties I should be checking before going down that road.

Thanks.
Chad

I understand. Unfortunately, I can't provide any help with this. Performance is one of the reasons we avoid this like the plague. Sorry I can't help more. Good luck to you.

Kelly

We stored our user accounts in a field in HR11 (Clock Number). We did that because we use ProcessFlow to create user accounts, so when our security system creates a user account on the network, it updates the Lawson field right away. Maybe something similar would help?