recently there was a change in Bigquery UI and it seems that is no longer possible to schedule a stored procedure to execute automatically.
Using the UI, just keeps asking to insert a destination table. If I put a dummy table, the schedule is created but then when tries to execute just throws an error saying that we can't have a destination table when executing a stored procedure.
Is anyone having this issue and has any kind of workaround ?
Thanks in advance.
You can opt out of the preview features by clicking the Hide Preview Features button in the top bar of the UI.
This is a known issue that the BigQuery engineering team is already aware of and are rolling the fix for it soon. You can follow their progress on this Public Issue
Related
Perhaps better to rephrase my question.
If I have a powerbi report..
Can I somehow make copies of this report with different data(set?) via an API and on demand?
e.g.
User requests a report with some parameters,
Existing report gets copies with a new dataset and published
tnx
Brian
== origional question below ==
Would anyone be able to point in in the right direction here.
I currently have a c# application that generates reports which are simply excel files.
Each time I create a report I simply open an excel file with some preexisting formatting, set the data in a particular sheet then save it to a new location.
How can I achieve something similar with PowerBI?
Ideaily I'd like to open a precanned powerbi report, pass a parameter to the 'dataset' I've just generated,
I dont have any string feeling as to what the dataset would be, I'm open to whatever works,
database/static dataset created by csharp somehow/webservice/etc.
Can anyone suggest how? tnx
How about creating you Power BI report based on your existing Excel files? Make sure to store them on SharePoint so that the PowerBI Online Service can pick them up w/o additional gateways. You can then use your app to trigger the report refresh as soon as the Excel files have been updated.
In the cloud console, I created a new Cloud Spanner View called StudentView which left joined my Student table and a ClassEnrollment table. The update seemed to work as I could see the new View created.
I then looked at my Students table and I got the error:
Cannot read properties of null (reading 'join').
View screenshot of error
The Students table showed no data even though it is populated. I subsequently deleted the StudentView:
DROP VIEW StudentView;
The result is still the same and the Student table displays nothing but the error stated above - even though the StudentView has been dropped.
I have also tried replacing the StudentView View so it does not contain null values, but the error persists.
I am assuming the error refers to the View that I created. If that is not the case, please could you point me in the right direction.
Any idea how to go about this problem?
There was a short-lived bug in the Cloud Spanner UI that was active around the time you asked this question (2022-08-30). Assuming you can see Students now, and StudentView doesn't appear in the UI anymore, the bug probably affected you too. Nothing you're doing wrong, just unlucky timing.
If you ever suspect there's a problem with the Cloud Spanner UI, you can list and query DBs with gcloud spanner .... In this case gcloud should have continued to work while the UI was down.
I am having an AWS personalize solution with 3 successful solution versions trained with trainingMode = "FULL" using both AWS console and AWS SDK python. However when I tried to create a new solution version with trainingMode="UPDATE" as shown in the code below:
import boto3
personalize = boto3.client('personalize')
personalize.create_solution_version(solutionArn = solution_arn, trainingMode = "UPDATE")
I've got back the following exception:
Exception has occurred: InvalidInputException
An error occurred (InvalidInputException) when calling the CreateSolutionVersion operation: There should be updates to at least one dataset after last active solution version with training mode set to FULL.
Anyone experiencing this issue, is there anything I miss to be able to train with an UPDATE mode?
The purpose of trainingMode="UPDATE" is to process new items added to the items dataset (via PutItems or a bulk upload) as well as impression data for new interactions added to the interactions since the last FULL/UPDATE training. The new items and impressions are used to update the exploration feature for solutions created with the aws-user-personalization recipe. That is, to bring in new/cold items for exploration and to adjust probabilities for existing cold items in further exploration. Note that UPDATE only brings in new items and impression data and does not retrain the model.
Therefore, if there are no dataset updates since the last FULL/UPDATE, there is no value in creating a new solution version with UPDATE.
Finally, keep in mind that Personalize automatically updates solution versions created with the aws-user-personalization recipe every two hours at no cost. This essentially does an UPDATE for you.
With User-Personalization, Amazon Personalize automatically updates the latest model (solution version) every two hours behind the scenes to include new data without creating a new solution version. With each update, Amazon Personalize updates the solution version with the latest item information and adjusts the exploration according to implicit feedback from users. This allows Amazon Personalize to gauge item quality based on new interactions for already explored items and continually update item exploration.
If you create a solution version with UPDATE, you will be charged for the server hours to perform the update. Practically speaking, the only time you would need to manually create a solution version with UPDATE is when you do not want to wait for the next automatic update.
I haven't done any changes in my dataset for a while and in the past few days, the refresh and publish features (via PBI Desktop) were working just fine. However, this morning, it suddenly stopped following through the scheduled/automatic refresh which were set 5x a day every 2 hours starting 8AM. When Itrigger manual refresh, it says "Preparing for refresh" but doesn't really follow through with it, so i kept on clicking it but to no avail. After a while, I checked the Refresh History and the error I got was it's timing out.
I was trying to republish it with a newer version which was the same dataset refreshed in a different workspace. Apparently, when I publish it to a different workspace, or if I rename it and publish it to my existing shared workspace, it works. BUT I don't want to push through with this kind of workaround because I cannot afford to redo my the set up of RLS and manage permission in the dataset of my existing workspace.
Hope you can help me on this. Thanks.
Try signing in to the workspace using a browser, then use the Get Data feature (arrow button at bottom left), then choose Files / Local File and select your PBIX.
It's effectively the same results as a Publish from Power BI Desktop, but sometimes the method above works when Power BI Desktop is jammed up.
You might also have a refresh issue, not a publish issue. There's an unannounced-refresh-on-publish feature that most people don't notice:
"When you republish a dataset published from Power BI Desktop and have a refresh schedule defined, a dataset refresh is started as soon as you republish."
https://learn.microsoft.com/en-us/power-bi/create-reports/desktop-upload-desktop-files
Every time I'm composing queries in the BQ UI, if my mouse hovers over a column name after I've typed it in the query editor box it brings up the column name and type in a little window.
Does anyone know how to stop this happening as it's super annoying when trying to edit queries with the stupid popup constantly coming up??
screenshot:
Try using the BigQuery UI within the Google Cloud Platform Console as the query editor doesn't have the column information pop up. Keep in mind that as it's a beta release the popup may be present in future releases and consider its limitations.
I suggest opening a Feature Request about having an option to enable or disable this pop up within the Google Issue Tracker for both BigQuery UIs.