u/CPD-LSF

https://preview.redd.it/q95fbly3pakh1.png?width=625&format=png&auto=webp&s=6d5882884ee0f541954b77cc869dfc62faaa2e46

This is now appearing above individual schedules for me. If I pass a variable from a local variable library to it and it's boolean = True it enables the schedule.

I have created 3x variables called dev_schedule, test_schedule and prod_schedule, then in the DEV pipeline I create 3x schedules and point to each individually.

It means when I promote to TEST and PROD only 1/3 of the schedules are activated meaning I can finally deploy pipelines without messing about with schedules once they hit the intended stage as they just work.

For context I saw a post from a user showcasing a Fabric App with writeback, but I understand it's basic writeback to the Rayfin DB, not like an actual delta table in Fabric.

For clients in the past I've used a mix of:

- CSVs uploaded to the Lakehouse - attaching to a structured load process to pull these in once per day

- Dataverse tables users can access which are loaded to Fabric periodically to be utilised afterwards

Is there a best practice you go with, or general tool you use that you rate highly as an alternative to this? I'm talking data which may be used for mappings to enrich data out of structured systems like D365 for instance. Some companies also require manual adjustments that aren't housed in their main ERP due to development gaps or it just not being justified financially.