feat: Excel Attachment Parse to JSON #147 #153
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
feat: Excel Attachment Parse to JSON #147
This Flow Designer Action accepts the sys_id of an attachment file and converts its multi-sheet data into a structured JSON string. This enables easy record creation, transformation, and integration downstream in any Flow.
Action Inputs
Logic
The core logic is contained within a single Script Step named
Parse Attachment Content. The script prioritizes robustness by first inspecting the file's extension and MIME type.jsondatastring).Action Outputs
Example JSON Data Output Structure (for multi-sheet files):
[ { "SheetName": "Sheet 1 Name", "Records": [ { "Header1": "Value1", "Header2": "Value2" } ] }, { "SheetName": "Sheet 2 Name", "Records": [ ... ] } ]Test Cases
The following test cases validate functionality using the provided DemoExcel.xlsx file (which is attached).
Positive Test Case
{Success: 5 records parsed across 2 sheets from file: DemoExcel.xlsx}Expected JSON Data:
Negative Test Cases