User Profile
hvdbunte
Frequent Visitor
Joined 1 year ago
User Widgets
Contributions
OneDriveSharePoint shortcut with library variables error
I try to dynamicly change the target subpath of the onedrive sharepoint connector for my environments (dev/test/ etc) So I would like to replace the target subpath with a library variable. my variable value: But when I change the target subpath value to the above library variable I get below error: Can somebody explain if this is still an issue because the connector is still in preview? Or how I could fix the syntax? Kind regards,Re: user data function with source control behavior
Hi v-prasare , Thank you for the reply, I am still not sure if my last post is the solution that would be the solution or what would be a best practice for working with source control and User Data Functions. Could you confirm if this is the case or not? Kind regards,Re: user data function with source control behavior
Hi, Mauro89 and MJParikh Hi, Thank you both for the usefull and thorough responses. MJParikh I agree with your reply but I did some further testing with the UDF connection. See below for details. Because I expected a silent rebind as you describe in your post and the names of the lakehouses are identical indeed. Mauro89 I also agree with your suggestion here, on other fabric items this is working but in my testing not with a UDF. Because if I try to work with a UDF and connect to the lakehouse in DEV workspace in my feature branch, I followed below steps, I get an error, see screenshots. So what I tried doing: - I made a feature branch from main with source control > branch out to workspace - in the feature branch I created a new UDF with a connection to the lakehouse in the dev workspace, that has the same name in dev and feature workspaces. And queried some data from the lakehouse in the dev workspace. - Published the udf. - with source control I committed the udf to git. - created a pull request to merge into the main branch - update the main branch from source control. - I opened the UDF in main branch and ran my test. I still get a commit in main. - commit the change to main branch with source control I see a change in de definition.json, see below: But the lakehouse in DEV has this ID (2ce75851-c895-49ea-87c6-32ed1b990e3a). The artifactId on the right side of the screenshot I cannot find in my workspace (DEV or feature). - With a pull request I synchronized my feature branch with main. - when I update the feature branch through source control. I get the below error message So I’m still not sure what the best practices are for working with UDF’s and GIT. For now I would suggest creating the connection to the feature branch and the binding will be correct. But for other Fabric items this is not the case. I hope it is clear what I try to achieve. We are thinking of using UDF’s for error handling functions etc with multiple developers and are testing all fabric items and git integration. And this is some behaviour we didn’t expect. Again thanks for your replies Kind regardsuser data function with source control behavior
Hi, I am using a user data function in a workspace with git integration. We have the following senario: - I made a feature branch from main with source control > branch out to workspace - in the feature branch I created a new UDF with a connection to the lakehouse in the feature branch. And queried some data from the lakehouse in the feature branch. - Published the udf. - with source control I committed the udf to git. - created a pull request to merge into the main branch - update the main branch from source control. When I check the main branch I get the following issue: There is a commit for the UDF. That’s something I didn’t expect. Other items don’t need to commit back in the main branch. Does anybody know why this is happening? Is it because the connection change needs to be committed? from feature branch connection to main branch connection of my lakehouse? I hope somebody can explain the behavior, if more information is needed please let me know Kind regards,
