A couple questions regarding v9 to v10 upgrade

Hi all - a newbie posting here.

We are in the process of migrating from v9 to v10 Lawson financials -- hosted by Infor.

We've come up with a couple of questions/potential issues, and I'm curious if any of you have already encountered them.

1. Regarding Microsoft Office Add-Ins, our organization is still on Office 2010, which is not on list of supported Office versions for Add-Ins v10. There's been a little bit of ad hoc testing using Office 10, which has worked thus far. Our plan is to test Add-Ins against an install of Excel 16, leaving Office 2010 in place.

Of course, since Add-Ins v10 /Office 2010 isn't on the compatible list, Infor doesn't have any information about what might go wrong.

Has anyone encountered this scenario before? I'm trying to quantify the risk as best as I can. (I personally want to go to a supported configuration, but still haven't done inter-operability testing yet with a stand alone Excel 2016 layered onto an existing Office 2010 install. (We are on SharePoint 2010, as well, and some of the add-in files are stored there.)

2. In our v9 instance, we use several shared drive locations to temporarily store files that are in transit as part of our process flows. Infor informed us that their Cloud governance body does not allow shared drives on v10 instances. But they also haven't yet defined an alternate solution for loss of the shared drives.

Has anyone come across this obstacle, and how'd you address it?

Thanks in advance for your input.

Kevin Young

Find more posts tagged with

Infor Lawson Financials Group - Discussion

Comments

Legacy Contributor

We experienced no issues with Office 2010 during testing. However, we used the Lawson upgrade to help move along the Office upgrade across our organization. We went live with v10 after most devices had been upgraded to Office 2013, and have had no significant issues.

Legacy Contributor

Kevin,

We went live on v10 cloud on 9/25/17, so in regard to your #2 question, I can tell you how our shared locations now work. Infor gave us access to certain areas of both the LSF and landmark servers. The directories we have access to (via FileZilla and FTP account set up by Infor) are any standard Infor directories that programs may write to. Examples would be work, HHT, interface etc. on the LSF server. In addition, we gave them a list of custom 'shared' directories that we need. They initially created them for us, but now we can add, delete as necessary via FileZilla. If we need to download a file to our network from the cloud server, we also do this via FileZilla.

Infor created numerous FTP users according to what we needed. For example, our Finance dept has one that can only get to the work and print directories.

This was all an adjustment in how we move files around, but it has worked out fairly well thus far.

0712050809193544.doc

Legacy Contributor

we are using WinScp to access our previous shared drives. The FTP access was setup by Infor. The add-in issues we experienced was that we needed a newer version of the add-in from Infor support. The conversion of version 9 to version 10 add-ins was also a challenge at first.

Legacy Contributor

Thanks, Mary Beth. Would you happen to have the use cases that were tested for Office 2010 on Add-Ins v10? If I'm understanding correctly, it sounds like all your Add-Ins users would have been migrated to Office 13 before the v10 upgrade?

Thanks,

Kevin

Legacy Contributor

Thanks for the information. Would you be able to describe what kind of challenges you encountered in the add-ins 9-10 conversion - anything we should be watching out for?

Thanks,

Kevin

Legacy Contributor

Thank you --

We hope to hear next week how Infor intends to solve for "shared" drives not being allowed. I'll share this response with our Process Flow developer for context.

Thanks,

Kevin

Legacy Contributor

As another note for your PF developer, if you need to transfer files from LSF to landmark, you have to use the FTP node. You cannot use the move, copy etc. in the SysCommand node. Also, if you want to email a file that is on the LSF server, you have to FTP it to the landmark server first. You cannot directly email a file on LSF w/ IPA. Also, the FTP node does not have the capability to delete a file once it has transferred it. So, if you FTP an interface file from LSF and then need to delete it, you have to do that with the FileAccess node. I logged an enhancement request to allow the FTP node to delete (per Infor's recommendation).

Legacy Contributor

Apologies for a very delayed response... I don't have a list of use cases to share. We explained to our users that they need to test any critical functionality with the add-ins, and there are several weekly functions that are handled in AP, HR, PR, and Supply Chain. From an IT perspective, we tested various queries and uploads as part of our standard application and integration testing of the v10 upgrade. Also - you are correct, we migrated to Office 2013 before the v10 upgrade. Even though we did not experience issues, we knew that if/when we did we would be told that the version we were running is not supported on Office 2010; better to be on a supported version.

Copyright © 2025 Infor. All rights reserved.