Issue while populating Excel columns dynamically in Microsoft Excel Input using Get File Names output in AutomationEdge Process Studio

Get Help & Discuss
, , ,
1

Hi everyone,

I am facing an issue while dynamically reading an Excel attachment in AutomationEdge Process Studio .

Current workflow:

Email Messages Input
→ Get File Names
→ Rename Fields
→ Microsoft Excel Input

What is working correctly:

  • Email Messages Input downloads the attachment successfully

  • Dynamic mail folders are created correctly

  • Get File Names identifies the Excel file correctly

  • I kept only the filename field using Rename Fields

  • Hardcoded filepath works fine in Microsoft Excel Input

Problem:
When I enable “Accept filenames from previous steps” in Microsoft Excel Input and pass the filename dynamically, the data gets shifted incorrectly.

Example:

  • filename value goes into EmployeeID

  • EmployeeID goes into EmployeeName

  • EmployeeName goes into Date

  • etc.

Finally I get errors like:

“Conversion error: Index 35 out of bounds for length 5”

It seems like metadata/stream fields from previous steps are getting mixed with Excel row data instead of Microsoft Excel Input consuming only the filename field.

I already tried:

  • Removing extra fields using Rename Fields

  • Keeping only filename field

  • Rebuilding fields from header row

  • Mapping using column names

  • Using regex wildcard for xlsx files

Still facing the same issue only in dynamic mode. Hardcoded filepath works correctly.

Has anyone faced this issue with Get File Names → Microsoft Excel Input flow?

Any help or suggestions would really be appreciated, please help me.

2

Hi,

Could you please try placing the Rename Fields step after the Microsoft Excel Input step instead of before it?

For example:

Email Messages Input
↓
Get File Names
↓
Microsoft Excel Input
↓
Rename Fields

In the current flow, the filename field is being passed into the Microsoft Excel Input along with the incoming stream. This may be causing the input field metadata to get mixed with the Excel output fields, which could result in the observed field shifting.

With the above approach, allow Microsoft Excel Input to process the filename directly and perform the field renaming/removal after the Excel data has been read.

Please try this once and check whether the filename field is still present in the output. If the issue persists, please share the Microsoft Excel Input configuration and the output fields from the step for further investigation.