Skip to main content
Question

IFS Cloud Excel Add-in 23R2

  • 8 March 2024
  • 8 replies
  • 173 views

Hi,

We are currently upgrading from IFS to IFS Cloud.  We currently have a number of Excel migration jobs to support users in their daily work.

I have overcome most of the issues encountered so far aside from the following:

The Search functionality always throws a Malformed Request error.  Thereafter, nothing related to the Excel add-in works anymore without logging off/on again.

Has anyone else encountered and found solutions to these issues?

 

Thank you.

 

 

8 replies

Userlevel 2
Badge +5

hi,

Can you please post a screenshot of search dialog with specific search which you have used?

Thanks you!

Badge +2

Hi,

 

 

Searching for a particular part:

Searching for part 

Upon pressing the Search button error occurs, and everything ceases to function:

 

Migration job details:

 

 

Best regards,

Pakorn

Badge +2

Hello,

I have been doing some extended testing.

Apparently the add-in search has issues with special characters like ‘#’, which is unavoidable for us.

Is there a solution to this?

 

Thanks.

Userlevel 5
Badge +15

Hi @pacharry ,

I have been doing testing in the 23R2 Core environment with latest SU and same error is raised.

Please, open a support case so this can be investigated further or a workaround or solution can be provided from RnD.

Regards,

Pilar

Badge +2

Hi @pacharry ,

I have been doing testing in the 23R2 Core environment with latest SU and same error is raised.

Please, open a support case so this can be investigated further or a workaround or solution can be provided from RnD.

Regards,

Pilar

Thanks.  I have raised a support case on the matter.

Regards,

Pakorn

Userlevel 7
Badge +21

@pacharry That is a pity to read that the # doesn't seem to be working in searches. I'm wondering about the following:

  1. Will using an underscore at the position of the # help? So search criteria will be NSWTPHF46_F
Badge +2

@eqbstal .  IFS R&D has recognized this as a core issue.  It is reported as solved in:

  • 24.1.0 - 24R1 GA
  • 24.2E.0 - 24R2 EA

Best regards,

Pakorn

Badge +2

This same issue appears to me when I modify the Source Columns in the Migration Job, so they appear different in the Excel Spreadsheet. Aren’t these meant to be modified?

Reply