I got bunch of .delta table which in need to save as .json and zip them together to submit it tothrid party tool for futher processing. I was able to get all .delta tables into .json files in a single folder,. My consolidated .json folder is 'Files/temp/consolidated/' (see image below), but when trying to zip them together getting error: not able to find path with zipf.write(json_file_path, arcname=f) code: with zipfile.ZipFile('sample.zip', 'w') as zipf: for f in filenames: json_file_path = f"Files/temp/consolidated/{f}" print (json_file_path) zipf.write(json_file_path,arcname=f) what i learnt was: Microsoft Fabric Context: The Fabric environment uses a virtual file system, which doesn’t provide direct file path access as in traditional file systems. zipfile.ZipFile.write Limitation: This method expects a direct file path, which isn't available for Fabric paths. Any one had this scenario, how did they get around it?

Hi Everyone, Has anyone experienced issues with folders or files being deleted in Fabric Lakehouse? I had a folder named 'Attachments' in the Lakehouse, which contained around 350k documents as part of a data migration process. These documents were converted from base64 strings and saved in the Lakehouse folder. However, this folder has now disappeared (not sure how :)). Does anyone know how to track the audit to determine what caused its deletion or if there's a way to restore it? Raised a ticket with MS and awaiting response. MS doc on Soft delete for Onelake files : https://learn.microsoft.com/en-us/fabric/onelake/onelake-disaster-recovery#soft-delete-for-onelake-files

Newbie question- I’m assigning values to variables in a notebook and I want to submit those variables as parameters to another notebook. What is the recommended way of doing this? Thanks

Happy Monday to all the Fabricators! I'm interested... what are you building this week? Any blockers that we can help with?

Just wanted to know how others are dealing with creating surrogate key with auto-increment in delta table. Seems this is something supported in Databricks, but not in fabric. in Databricks: CREATE OR REPLACE TABLE demo ( id BIGINT GENERATED ALWAYS AS IDENTITY, product_type STRING, sales BIGINT ); Going forward, the identity column titled "id" will auto-increment whenever you insert new records into the table. You can then insert new data like so: INSERT INTO demo (product_type, sales) VALUES ("Batteries", 150000);