I'm trying to create a custom visual in Power Bi using Python script. My data source is from my excel file and it load properly. But whenever I will type my script in the python script editor and execute it, it always giving me the same error of can't display this visual. Anyone who can help me resolve this?
Error Message
Script
I finally solved the same problem thanks to frustration. The working solution felt impossible to me as a python coder. I though I was supposed to modify the two automatically generated dataset related comment lines to code by deleting the \# from the beginning of those lines.
How my code looks like now and display works as expected:
\# dataset = pandas.DataFrame(.. ! keep this line as a comment !
dataset = dataset.drop_duplicates(.. \# this line you can run or leave as a comment
.. my code ..
This error happens mostly not only because of a connection to a python script but also connections to SQL connector or even just an update from Power Bi. Check the recent changes in Power BI every month to see if any affect your problem. Also, check your transformations and data types. You may be using text instead of the Whole Number for enumerations
Related
My bubble map is giving an error, it does not load.(After my PC restarts for updates.)
This has happened before, when creating other dashboards also if a map was inserted, after I closed and reopened Power Bi.
I've tried searching in other places, and it says to go to https://app.powerbi.com/admin-portal/, but it is BLANK.
I tried to enable some map-related functions within Power BI, but also without success.
The issue is that in addition to giving an error, Power BI also does NOT allow me to reconstruct this visual map on the same dashboard.
Has anyone ever experienced this?
Here is the link to the IMAGE of my error! The error message is in Portuguese and it says to check the Admin Portal on https://app.powerbi.com/admin-portal/ , but when i do it, all I find is a blank section instead.
Thanks.
I am trying to change formatting within an excel spreadsheet using SAS.
However, being a complete beginner to SAS, not sure how to go about it.
Googling lots made me get 'ODS Excel' and 'ODS Excel XP' as possible approaches.
'ODS Excel' is giving me corrupted files though, so I'm skipping that one.
Could someone please advise in detail on how to do something like below within each step I have written, preferably using 'ODS Excel XP'? Or if I am doing something wrong with 'ODS Excel' in my syntax, happy to use that as well.
Input file: /myfile.excel/
SAS:
Step 1: Read myfile.excel, which looks like this
Step 2: Turn the title row into bold text and that whole row yellow in colour, not just the cell with the text
Step 3: Output the formatting changes to new or existing excel, I don't really care
I have no idea how to do this in SAS. Could someone help, please?
Thank you!
Update: This is my SAS version: Custom Version 9.4_M3
Yesterday i was editing a couple of tables and these perfectly worked.
Today i turned on my pc and when i accessed to the PowerQuery Editor it returns me an Error message but it just appears in the PowerQuery Editor.
The thing is that i can still work with these tables on my dashboard but i can't edit them in the PowerQuery Editor
I can't understand why this doesn't work. It took me a long time to edit the tables and when it show me message to go to the Error i modify or delete the part that returns me the error i close the application and get into again and the same happens.
Here i show the table out the PowerQuery Editor
Here i show the Error that returns me when i get into the Power Query Editor
That error seems pretty self explanatory - column ' Todas las APTs' isn't found in your source data.
I'd suggest checking the source file, to see if your data content has changed, then change your query accordingly. It may be worth trimming your data before promoting headers, to eliminate those multiple spaces before the actual column header.
I just downloaded Power BI desktop.
Opened my reports and for some reason all commas in measures are now pipes (|).
If I try to use comma it gives me an error.
If I open the same report on another server then I see commas, no pipes.
What is going on?
It seems to come from a local configuration. Can happen on Excel too. Usually you can modify the parameter "Region and Language Settings -> Additional settings..." and check the format on List Separator.
The problem can happen when you open a wrong formatted CSV file.
Will make this short and sweet - we have a massive .CSV that we are linking to PBI Desktop. Some of the header names in this .CSV were not optimal and have since been updated by the SQL backend. However, PBI is not happy with not being able to find the exact header that existed previously, and we could not find a route by which to tell the software that a header name had changed. Is there a quick solution for this?
Here is an idea to work around this issue,
as long as your header are changing, I recommend you to do these step in power query:
search on your power query the step where the headers are promoted
instead of this step, delete the first row (the one containing the headers)
Then add a step renaming the header as desired
Hope that helps
Quick.. Not so much. Easy? Relatively.
You'll need to manually edit the PowerQuery in the Advanced Query side.
I recommend un-hiding the formula bar in the Query Editor and going step by step through the applied steps. Once you find a broken step, check out the PowerQuery, you'll see your no longer existent fields there as plain text in the formula bar ( or advanced editor view ). Swap out the old field names in the PowerQuery with the new names and you should be golden.
You might even get away with a few find/replaces..
You can fix this if you delete your top rows in your first row operation in query editor. This way the CODE of your power BI query will not contain a specific name and will name your columns: 'column 1' ; 'column 2' etc.etc.
You can now edit to your own demands and when you change datasource nothing will go in error.
Hope this helps for people who are also looking into the problem.