-
Notifications
You must be signed in to change notification settings - Fork 71
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
Data source error: column does not exist in the rowset. #56
Comments
Yeah, the main challenge with that endpoint is that MSFT doesn't provide any sort of list of possible fields that could come up from it, so what the connector does it that it implements some heuristics (using Table.Combine) based on the fields available when you create your query. There are 2 ways to avoid these:
|
Thanks for the quick response Miguel. I removed all the steps and monitored these 10 days, it is still failing with a similar error. I will check and follow your suggestions to see if something would work, Otherwise I will exclude this table and use other queries. thanks a lot, this is very useful for my case. |
@migueesc123 Can you please elaborate on the suggestion to: |
I don't have any resources, but basically what I'd suggest is to learn more about what partitions are in SSAS Tabular and how important the schema is. |
I was able to get incremental refresh working on the Event Activity Log API connector using the advice from your blog post about SharePoint. I was able to figure out how to define the default fixed schema in M. I specified the columns I wanted from the function, then created the empty table with same schema, as a fallback. **
** Now I have a PBIX in the service with incremental refresh running on any window of time that I choose! Yay! |
You inspired me with your solution, however I wanted the highest common denominator and not the lowest. I would like to share my solution with you, first I manually executed the EventActicityLog API with the maximum time interval of 30 days to get the maximum table structure.
This code first defines the table schema that contains the expected column names. Then, it checks the available columns in the retrieved table of the Event Activity Log, and only selects the existing columns. If at least one column is available, it selects only the existing columns and appends them to the predefined table schema. If no columns are available, it returns the original table unchanged. By using this technique, you can ensure that your Power BI queries are error-free and provide reliable results, even if the data format changes or is updated. |
Hi @migueesc123,
Since ActivityLog is looking for ActivityLogType for the given range, I am seeing these kind of errors on a timely basis. The refresh works without any issue from PBI desktop for same date range (I am using last 30 days). From Power BI service it works sometimes, but an error would occur, I assume when some activity type is not part of the range (?)
Can you please help on how to resolve these?
Data source error: | The 'ExportedArtifactInfo' column does not exist in the rowset. Table: Event Activity Log.
Data source error: | The 'WorkspaceAccessList' column does not exist in the rowset. Table: Event Activity Log.
Thank you.
The text was updated successfully, but these errors were encountered: