I am a SAS newbie and use EG because i'm not a SAS programmer. There are options in query properties under Code Submission that says 'Use grid if able' and 'Allow parallel processing on same server'.
I have to pull data from large datasets and would love to speed things up on the grid but every time I check these boxes, I get an error. Can someone tell me what I can do to set this up?
Thanks
Jeff
Related
I just begun working on a project and have been tasked with translating some reports. I have found a handful of ways ranging from manual dataset translation to scripts and such. I was wondering, if there is some way of automating this process. Is there a way of taking an existing dataset, running some commands or something and with a few steps, have a translated report. My team has these reports embedded and there is a language code in the URL, perhaps there is some way of making use of that.
The dataset, that I am testing and trying to get it to translate consists of 4 tables and column names are only values with text, everything else is numbers. Logically, numbers don't translate, so columns are only necessary. There are also some visual titles, that should be translated.
I appreciate any help and any efforts made to resolve this.
For an embedded report, there's a couple of things that you can do:
Use translations files in the PBI model to handle measures and column names. These will show up as labels in visuals. See the section, Translate Power BI field and table names, here: https://pbi-guy.com/tag/tabular-editor/
The language can be selected from the app by putting it in a querystring: https://community.powerbi.com/t5/Developer/Setting-language-and-locale-for-embedded-report/td-p/606714
Add a table with translations for labels and titles. See this section from the same link above: Create one report and a “translation table” to display the right language. Note that a filter will need to be set by the app to select the language in addition to how the language is set in the querystring above.
A couple of important caveats:
Anything overwritten in the report will override a translation. So if you change a column name in a visual, that's what it will always be no matter what language is selected.
Not every visual supports expressions, so sometimes you'll have to wrangle a button or multi-row card to use as a label or title.
the free version of tabular editor can be found here: https://github.com/TabularEditor/TabularEditor/releases/tag/2.17.2
I'm new to PowerBI, and am working on a large database. I am attempting to prepare the data in the PowerQuery Editor.
I would like to code as many steps as possible, as analysing each column manually is extremely time consuming.
My coding goals (in order of priority):
For each query I would like to get their column quality.
Ideally, I would like to export the header names with the column quality, so that I can determine which are relevant. Furthermore, I can also use the column names to determine which column relationships might be relevant. The database is huge, so simply just importing all the data and trying to work with it from their is not feasible, in fact PowerBI comes up with the error that I don't have enough free memory.
I have VBA and some SQL experience.
I know I have a lot to learn w.r.t. PowerBI, and I am working on it, but need some guidance and direction, also on what is possible/feasible.
Any contructive hints, advice, or feedback would be appreciated - thank you!
Use Table.Profile() on each table and load to the data model.
https://learn.microsoft.com/en-us/powerquery-m/table-profile
Guys this is a bit of newbie question. Ive tried to google it and understand how they work but im not having much luck. I have a datasets created by colleague that connect to one of our systems.
I want to look at using it and trying to make some changes. I can see Its create a .pibx file when i saved a copy of the dataset. i want to look at model section and see if i can pull some further fields(column) into table on the dataset that already links some corresponding data from two other tables. Id like to add more fields(columns) that are not currently in that table
However i don't want to affect other datasets and or the data on the system it is communicating with.
Can anyone advise me if this is the case.
As i really only want to test things for now and not make any changes that might affect other people
You can create duplicate for original table( Query ) then play with that duplicat
How to identify the dataset of a report is based on. We have been using a powerbi work space since long time. There are multiple data sets and reports were added over the time. We lost track on what reports are using which data sets, and like to clean up if there are any used datasets.
Thanks
Jyothi
"View Related" Option on right side top corner will provide the data set information.
Hopefully someone out there will have run into this before. I'm trying to use the street level geocoding capability of SAS' PROC GEOCODE, but I keep getting a cryptic error. I couldn't find anything on the net about it (although to be fair I only spent a half hour looking).
First, I'm using SAS Enterprise Guide (I've tried on both v4.2 and v4.3), although I still prefer to program as I find the point and click interface quite limiting. Maybe this right here is my problem?
Anyway I first get the lookup data sets from http://support.sas.com/rnd/datavisualization/mapsonline/html/geocode.html and follow the instructions in the readme. I also use the pre-written SAS program to import the CSV files. My input dataset contains just 4 variables: street address, city, state, and zip. I then run the following code:
libname josh 'C:\Users\Josh\Desktop\Geocode\SAS files';
proc geocode
method=street
data=SASUSER.Home_Policy_Address_Detail
lookupstreet=josh.USM
out=test;
run;
However I get this error:
ERROR: Variable NAMENC not found in JOSH.USM data set.
Nowhere in the readme or the import program is a variable named "NAMENC" ever mentioned. This is what has me stumped. Is it something wrong with the simple PROC GEOCODE program I wrote? Is it due to me using SAS EG (although I've yet to run into a base SAS procedure that hasn't worked on EG)? Or something else?
Any help/guidance would be much appreciated. Thanks in advance!
Check your SAS version. You can use the 'Help' menu in DMS mode or submit this statement:
%put &sysvlong;
It looks like you are using SAS 9.3 but your lookup data JOSH.USM is the lookup data formatted for SAS 9.4.
PROC GEOCODE street lookup data comes in two slightly different formats, one for SAS 9.3 and another for 9.4. When you download the nationwide lookup data from the SAS MapsOnline geocoding page, make sure to download the version appropriate for your SAS release.