Skip to main content
Question

Fanning out from into excel tabs from different schemas

  • February 24, 2025
  • 5 replies
  • 57 views

p_c_20
Contributor
Forum|alt.badge.img+8

Hi. I’ve built a data cleaning workspace that performs a number of different tests, creating or retaining different attributes for each. I’ve created an ‘error type’ attribute to fan out by, have added schema scanners and have followed the gist of this. However, I cannot seem to get the writer to respect the varying schemas for each tab. Set up like this: 


 

 Pointers appreciated. 

Many thanks

5 replies

liamfez
Influencer
Forum|alt.badge.img+34
  • Influencer
  • February 24, 2025

Do you have a different SchemaScanner per path that will each create a different tab in the xlsx? If you are only using one SchemaScanner for multiple error types that could be the issue, in which case you would probably need to use GroupProcessing to create a schema per error_type.


bwn
Evangelist
Forum|alt.badge.img+26
  • Evangelist
  • February 25, 2025

Note that when using a Schema Feature for dynamic writing, the Schema Feature needs to arrive before the data features.

Edit: Noted already done that above but leaving the note in the thread  😉

If routing from a SchemaScanner, then the Parameter “Output Schema Before Data Features” needs to set to “Yes” (and is a little weird this is not the default setting)
 

Similarly as ​@liamfez has noted, to create separate Schemas, one per Excel Worksheet, then need to have SchemaScanner Group Processing Attribute = Error_Type


p_c_20
Contributor
Forum|alt.badge.img+8
  • Author
  • Contributor
  • February 25, 2025
liamfez wrote:

Do you have a different SchemaScanner per path that will each create a different tab in the xlsx? If you are only using one SchemaScanner for multiple error types that could be the issue, in which case you would probably need to use GroupProcessing to create a schema per error_type.

I do have multiple SchemaScanners, yes. 


liamfez
Influencer
Forum|alt.badge.img+34
  • Influencer
  • February 25, 2025

If you are currently just using one xlsx feature type (that is fanned out), you could try copy/paste that writer feature type so that you have more than one on the canvas. So that each SchemaScanner is connected to a writer feature type. I am wondering if there is still an issue with the order of features arriving, if you have multiple schema scanners flowing into one writer feature type.


p_c_20
Contributor
Forum|alt.badge.img+8
  • Author
  • Contributor
  • February 26, 2025
liamfez wrote:

If you are currently just using one xlsx feature type (that is fanned out), you could try copy/paste that writer feature type so that you have more than one on the canvas. So that each SchemaScanner is connected to a writer feature type. I am wondering if there is still an issue with the order of features arriving, if you have multiple schema scanners flowing into one writer feature type.

..or maybe precede the Excel writer with a Sorter? 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings