-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no longer able to update the schema #139
Comments
I'll try renaming my workspace. I have a space on it. yep, this works when I replace my spaces with _ GUID is not working for me. the systeme is not able to find the workspace + lakehouse at all. it still try to add .lakehouse at the end while a guid access did not require it. |
Fabric have changed something in the API so with spaces it isn't working anymore. |
wow you are so fast!!! thanks a lot. |
Well thanks to @greglong1 and @lhammerbh who did all the checks 😄 |
Hi, unfortunately I encounter this problem even though I downloaded the latest release (if I'm doing it correctly; I downloaded the asset from 24.25 release: https://github.com/Bertverbeek4PS/bc2adls/releases When I enter the GUID then I already get an error on exporting schema: {"error":{"code":"BadRequest","message":"WorkspaceId and ArtifactId should be either valid Guids or valid Names"}} When I enter the Workspace name (which I altered to not contain spaces) then the export schema returns no errors but then the export does: Invalid format of GUID string. Not sure if I'm really on the fixed version, as it states 24.24 as version number instead of 24.25. AFAIK the GUID is in the address bar when visiting the workspace page: So: https://app.powerbi.com/groups/{GUID}/list?language=nl&experience=power-bi |
@GC-Martin when i switched the lakehouse to also be the GUID instead, that's what solved the issue for me. so i use the GUID on both the workspace and lakehouse. this is all new to me so i wasnt really sure which to download when it comes to the latest release as well but i just downloaded it straight form the main repository page as a zip, instead from the assets on the release page. |
@LumosPatronum thank you! That did the trick. I used GUID on both now. Regarding which to download; I am also not sure. I assume a 'release' is more stable than current state of the main branch, but for me this is also new. I don't usually work with github repo's nor did I ever create a BC extension. It would be nice if less knowledge was assumed and someone could add some installation instructions to the Readme. |
@GC-Martin thanks for confirming that worked, I had reported the same issue on #147 and Bert had said that he will look into it when he gets a chance. I was confused too since my lakehouse and workspace were all lowercase but yet it wouldnt work until i switched them both to be GUID. |
Hi @GC-Martin and @LumosPatronum. If you want to download only the app without you need to compile you can look in the releases for BC23 and BC24. |
Hi,
Today I'm receiving this error when I try to add table to my export config:
If requesting support, please provide the following details to help troubleshooting:
Error message:
Could not create blob https://onelake.dfs.fabric.microsoft.com//.Lakehouse/Files/GLAccount-15.cdm.json. {"error":{"code":"ArtifactNotFound","message":"Request Failed with Artifact '.Lakehouse' is not found in workspace ''."}}
Internal session ID:
Application Insights session ID:
Client activity id:
Time stamp on error:
2024-05-23T10:51:36.6300832Z
User telemetry id:
AL call stack:
"ADLSE Gen 2 Util"(CodeUnit 82568).CreateBlockBlob line 35 - Azure Data Lake Storage Export by The bc2adls team
"ADLSE Gen 2 Util"(CodeUnit 82568).CreateOrUpdateJsonBlob line 5 - Azure Data Lake Storage Export by The bc2adls team
"ADLSE Communication"(CodeUnit 82562).UpdateCdmJsons line 13 - Azure Data Lake Storage Export by The bc2adls team
"ADLSE Execute"(CodeUnit 82561).ExportSchema line 34 - Azure Data Lake Storage Export by The bc2adls team
"ADLSE Execution"(CodeUnit 82569).SchemaExport line 28 - Azure Data Lake Storage Export by The bc2adls team
"ADLSE Setup"(Page 82560)."SchemaExport - OnAction"(Trigger) line 4 - Azure Data Lake Storage Export by The bc2adls team
everything worked fine until today.
I just wanted to add new table in the export config.
but this is not working.
I tried to use GUIDs instead of lakehouse and workspace names, but the GUID are not recognized at all by the code. (maybe adding a flag like "lakehouse is guid" could help for that, as using a guid doesn't required adding .Lakehouse to the URL)
for sure I double check the security, and nothing changed and the data were exported until I stop the export to add new tables.
The text was updated successfully, but these errors were encountered: