When you have errors in your excel file, they sometimes leak through and adding "Table.ReplaceErrorValues" or "Table.RemoveRowsWithErrors" doesnt really work. What I have found is to add the error fix step right after the navigation step that loads the sheet.
In the screenshot below, I have used "Table.RemoveRowsWithErrors" after the Navigation step and it fixed the error.
We needed a new passport for our daughter as her passport expires in 5 months and 3 weeks from date of travel (country requires 6 months).
Panicking, we emailed our senators and representatives. Got a call from one of them and they advised to call passport phone number and tell them country we were travelling to needs a visa (urgent passport appointment is provided 28 days out for countries needing passport).
Time line
May 5: figured out we needed new passport. Called passport agency, was told to call back 2 weeks prior to travel.
May 6: emailed senators and representatives
May 8: got call back from one of the representatives' staff advising about calling back and telling them that we needed a visa
May 9: called passport agency and got an interview date for May 23 at Colorado office in Aurora. Lucky for us this is a 30 minute drive for us.
May 23: appointment was for 8am. Should have lined up 30 minutes early. Line was long, but efficiently managed. Had flight tickets, birth certificate (as passport was for kid and this is considered a new application and not renewal), paper work about needing visa. The entire appointment lasted less than 60 minutes. Was told to return after 2pm on 25th to pick up passport.
May 25: got passport (took 15 minutes)
Reflections:
1. Everyone we spoke to from the phone staff to the people in the Colorado passport office were extremely helpful, efficient and great to work with.
2. Didn't really need help from senator/representatives, but the help they provided telling us the provision for visa, was the breakthrough we needed.
3. Next time we will apply for passport 12 months prior to expiration, as many countries need 6 months validity on passport for travel.
4. Kids need a ds-11 and you are reapplying for a new passport (I believe until age of 16). Their passports are valid for only 5 years.
During a AWS CF deployment I got the following error:
Properties validation failed for resource LAMBDAXXXX with message: #/Code: expected type: JSONObject, found: String
After struggling for over 4 hours, it turned out that the issue was that the path was not correct in the CF Template!!!
How I hate CloudFormation!!!
Hope this saves someone else time!
Currently, there is no way to insert an image into a PowerBi report via PowerBi.com (power bi service).
One, workaround though, is to insert a "Blank" button and then set the "Fill" options Background
If you find that your deeplinks into a PowerBi report are not working, please make sure you are using a "?" in front of the "filter parameter.
More info: Filter a report using query string parameters in the URL - Power BI | Microsoft Learn
If you are coming from a Reporting Server environment, the filter url used to have a & in front of it, which will not work.
When testing, one easy way to see if your query parameter is working is to check your filter pane. The filter if correctly picked up will show up in there in italics. The following filters the report by a field named "District" in a table named "District". The table name and column names are case sensitive. The value used for filtering is not. Another tell tale sign that your url is not correct is if the filter gets dropped from the URL once the page loads.
?filter=District/District eq 'FD - 01'
Example of an old Report Server Link which will not work because of the "&": ?rs:embed=true&filter=District/District eq 'FD - 01'
We started getting an error with our Power Bi datasets that were using a Denodo connector. This seems to be happeing only with new files and not existing datasets.
The error we were getting is:
Unable to determine the data source. In order to determine details about custom connector based data sources, Power BI service needs to connect to a gateway, however, no gateway was available/reachable. Details: Static analysis failed in gateway. gatewayObjectId:e884ca97-b4d9-45bc-8560-ad3d2d4eaa56, resultCode:FailedWithUnknownOrUnsupportedDataSources Query contains unsupported function. Function name: Denodo.Contents .
Locally the PowerBi files works fine, this error shows up in PowerBi service after you publish the dataset and take a look at the settings for the dataset.
It looks like this might be a bug in PowerBI where when you add a new query that uses the Denodo connector, it is adding an empty list to the arguments and that is causing this is.
Source = Denodo.Contents("MyDenodoSourceName", null, []),
The problem is caused by the []. If you change the line to remove the empty [], then everything works fine!
Source = Denodo.Contents("MyDenodoSourceName", null),
Recently my car was blinking the maintenance minder B167 code.
Turns out each character has a specific meaning.
A quick post on setting up a connection to Athena with OKTA using JDBC. The SQL client I am using is DBeaver, but any other tool could be used.
jdbc:awsathena://AwsRegion=us-west-2;S3OutputLocation=s3://my-athena-results-bucket/results-folder/;AwsCredentialsProviderClass=com.simba.athena.iamsupport.plugin.OktaCredentialsProvider;user={user};password={password};idp_host=mycompany.okta.com;App_ID=0aosd2asadsdsdsd/123;SSL_Insecure=true;
This is a quick post on RLS behavior in a powerbi dataset, where you dont define any table filter expressions.
Basically, when you setup a role and you dont define any table filter DAX expressions, it allows you to control who has access to your dataset. This is useful, when you have multiple datasets in a workspace and you need to reduce the access to a particular group.
Here is an example:
Have you wondered how to use the "Create a report" >> "From a template" option from a dataset in PowerBi Service?
