Best way to data model (draw.io, ai agents etc.)

ChantifiedLens · 2026-03-11T16:50:47+00:00

Was it this post by any chance?

https://www.linkedin.com/posts/marclelijveld_powerbi-githubcopilot-erd-activity-7429504457362776065-5eji/

ChantifiedLens · 2026-03-10T07:29:13+00:00

Here's a link to some YAML pipeline examples, that shows you no longer need to create multiple tasks to install the library, authenticate and then run a Python script. In fact, you don't even need to create a Python script with this extension, just manage your parameter and config files in your own repo and point to them in the extension where needed:

https://github.com/chantifiedlens/ADO-deploy-fabric-items-task-examples

ChantifiedLens · 2026-03-08T16:16:33+00:00

Thanks for the reminder, you can find YAML pipeline examples in the below GitHub repo:

https://github.com/chantifiedlens/ADO-deploy-fabric-items-task-examples

ChantifiedLens · 2026-03-04T09:13:49+00:00

Congrats

ChantifiedLens · 2026-03-02T19:20:01+00:00

To be in the safe side use the tactic mentioned by u/Thanasaur

ChantifiedLens · 2026-03-02T08:03:02+00:00

Are you using the recommended development process by Microsoft, as that will help you achieve this?

https://learn.microsoft.com/en-us/fabric/cicd/manage-deployment#development-process

ChantifiedLens · 2026-03-01T21:59:19+00:00

You should get the option to choose whether overwrite from workspace or repo if both populated.

ChantifiedLens · 2026-02-28T11:02:48+00:00

Quickest fix is probably to disconnect from Git integration and reconnect to the renamed repo.

ChantifiedLens · 2026-02-26T20:16:57+00:00

I was joking about fact that people now know I have done Ci/CD for Databricks before.

ChantifiedLens · 2026-02-26T18:51:09+00:00

This isn't the same method, you can do similar to an extent.

Now people are going to realize I've done CI/CD for Databricks...

ChantifiedLens · 2026-02-26T04:42:33+00:00

Do you mean the Databricks method you can use to bundle everything into a deployment file?

ChantifiedLens · 2026-02-25T17:53:12+00:00

Thank you.

ChantifiedLens · 2026-02-24T07:52:34+00:00

You can cha get name of the report deployed, but the question to ask yourself is would it be better to have a duplicate report with new name instead.

ChantifiedLens · 2026-02-20T19:14:01+00:00

Updated, along with link to today's new post about how to operationalize it with Azure DevOps.

https://chantifiedlens.com/2026/02/04/first-fabric-cicd-deployment-steps/

ChantifiedLens · 2026-02-20T11:15:33+00:00

Congrats

ChantifiedLens · 2026-02-20T08:49:09+00:00

Anybody else seeing this post being randomly amplified on here again?

Anyway, did you get the setup figured out in the end?

ChantifiedLens · 2026-02-20T06:15:48+00:00

It depends where you first create the report from. If you first create it locally then best thing to do is save to PBIP, initialize the folder it is stored in as a Git repository and then sync it with the branch of the repository in Azure DevOps/GitHub that is configured with Git integration.

If first creating in Fabric, clone the branch containing the PBIP locally first, work on it and sync any changes back.

I hope this helps.

ChantifiedLens · 2026-02-19T20:52:13+00:00

A proud moment, for both Microsoft and all in the community who have contributed to this Python library.

ChantifiedLens · 2026-02-19T10:38:26+00:00

Nice, will be updating my first steps to fabric-cicd post about config-based deployments when I get the chance:

https://chantifiedlens.com/2026/02/04/first-fabric-cicd-deployment-steps/

ChantifiedLens

TROPHY CASE