What’s the best way to map field service report metadata to SharePoint folders?

[Gregory.J]

I’m trying to set up a system where our field service reports automatically populate the correct client folders in SharePoint, but I’m stuck on getting the metadata to map consistently. The workflow seems to break whenever a report contains multiple job codes for the same client. Has anyone else dealt with this specific data routing issue?

[Zoey19]

We had something like that last quarter. When a client showed two different job codes in one report, the routing rules would grab only one code and whisk the file into the wrong subfolder. It felt like the mapping logic assumed a single code per report.

[Aaron_H]

I tried a quick fix by hard-coding a primary job code and then falling back to the next one, but it was brittle and failed whenever new codes appeared.

[Mila.T]

Are you sure the issue is the mapping, or could something else in the workflow be the real bottleneck?

[OliviaDC]

I eventually moved to a two-step approach: first normalize the report to a single canonical code, then run the routing. It helped a little, though we never got full consistency and still saw edge cases.