This website uses cookies to ensure you get the best experience.
Learn more.
One pipeline should process different source tables using the same definition. Which design supports this?
Published
- Rename the source table before each run
- Parameters and dynamic expressions for table-specific settings
- Hardcode one table and copy the pipeline for every change
- Use a report slicer as the source-table variable
Comments — 0
Sign in to comment