So many tables in the fields/field tables, is there any methods to group them to folders, like the measure/measure group, and power query also can group tables/power query group.
Currently there is no such feature, but you can vote to implement it here:
Group Tables in Report View.
According to number of votes, it's not seen as super relevant by the users.
So, consider consolidating your tables and hide all the temporary ones from the view.
Related
I would like to allow users privileges by region with PBI DAX expression implementation to first get USERPRINCIPALNAME then proceed to get their region.
User Table:
Scenario:
When Shaun login to powerBI service. He only can view the dashboard and dataset in region R10.
If you have multiple tables you want to control with dynamic security, you might prefer an approach based on the propagation of the security filters through the relationships instead of using a DAX expression for every table you want to filter.
What we have to do is to create a new role and use this code to apply security filter for the user table :
[EMAIL]= USERPRINCIPALNAME()
The second thing to do is to apply bi-directionnal filtering for the relationship betwen user_region and region.
The following image shows a rough draft of my proposed database structure that I will develop for Django. Briefly, I have a list of ocean Buoys which have children tables of their forecast conditions and observed conditions. I'd like Users to be able to make a log of their surf sessions (surfLogs table) in which they input their location, time of surf session, and their own rating.
I'd like the program to then look in the buoysConditions table for the buoy nearest the user's logged location and time and append to the surfLog table the relevant buoyConditions. This will allow the user to keep track of what conditions work best for them (and also eventually create notifications for the user automatically).
I don't know what the name for this process of joining the tables is, so I'm having some trouble finding documentation on it. I think in SQL it's termed a join or update. How is this accomplished with Django?
Thanks!
I am not able to implement row level security to my report. I have tried different methods on google and Microsoft forums but all in vain. Could you please help?
I have a dataset name "Cases" which have details of all cases logged into system with its country.
Then I have dataset name "Escalations" with details of the all the escalations along with its country.
Then there is one more table called "Country Mapping" which contains all the countries mapped with their Regions and Region Manager.
I have already prepared a report showing Global /Regional numbers But now people want to restrict the data according to its own territory.
Example :- Some want to see global data and some are responsible for a particular country. I know RLS can help me with this. I have tried to make two tables one with Username and country responsible and other one with just usernames and names.
I have made a relationship between all these tables. But the problem with the code is, like if I am the admin of the report then I need to manually add myself in the country responsible for every country. Like 146 countries .
Is there any better way to do this?
I'm trying to produce a report in Power BI to count the number of groups an individual belongs to. I have a table with users, security groups they belong to, etc.
I'm looking to query the data to help track down users that don't belong to at least two security groups. In my environment every user should be in an All Staff security group plus any other unique group they belong to.
The image I've included has exactly what I'm looking for. I currently don't have that Total column. This is what I need help with. I have the Users and all of the groups they belong to.
Here's a picture of what I'm trying to achieve:
I've tried the Countrows command with a filter but I couldn't get it to filter based on the number of groups users belong to.
I can't simply count the number of times a user's name appears either because this table is a lot bigger than just my example above. This is just an extra feature I'm hoping to achieve out of my table - using the analytics of my report to help find group membership issues and resolve them.
To create the calculated column, you can use this code:
Totals = CALCULATE( COUNT(TableName[Group]), ALLEXCEPT(TableName, TableName[User]))
It groups records by 'User' and then counts number of groups per each user.
I'd recommend though to use measures instead of calculated columns. Measures are much more powerful and useful ways of reporting. To create a measure:
Totals =
SUMX(
VALUES(Data[User]),
CALCULATE(COUNT(Data[Group]))
)
Drop this measure into a matrix or a chart against the users, and you will have the desired report.
I have been trying to create a Schema for my Android application in Amazon Dynamo DB. I have very less experience with NoSQL Databases.
I have created a Survey based Android Application, now I have certain tables to store in Amazon Dynamo DB.
The Tables are Employees table, Survey table, Question table and the Response table.
The Employees table stores the information for all the employees, the survey table holds the name of the surveys and the employees, who has taken the survey.
My Issue is with the Question table and the Response table. The Questions are dynamic and are based on the employees who is taking the survey.
The answers in the Answer table depends on the number of Questions asked in the survey.
I want to know what should be my #DynamoDBHashKey, #DynamoDBIndexHashKey, #DynamoDBIndexRangeKey in the Question and the Response table, so that I can map question to respones and what should be the #DynamoDBAttribute in both the tables.
The Use Case can be: An Employee of the company posted 12 questions for all the other employees of the company.
Image was taken earlier, later on I added survey table as well
DynamoDB is good at some things and bad at others. Its great at scaling massively and horizontally while maintaining low read/write latency, but introduces eventual consistency, and forces you to make major schema decisions up front, such as what should be in a table, and how should data be partitioned, and what should be the indexes. It demands that you adopt its horizontal scaling model by partitioning your tables into pieces via the partition key.
From the way you have phrased the question it is clear that you are more comfortable in a relational database. DynamoDB is not a great place to start learning about NoSQL schema(less) design - I would have found it quite unforgiving if it was my first NoSQL database, especially trying to model a domain such as the one you describe. Its simply not a great domain modelling environment full stop - its all about horizontal scaling and performance.
If you are more comfortable in a relational database, then use a relational database. If you want to try NoSQL it is necessary to adopt a different mindset when it comes to modelling your domain into persist-able entities. For example, you might include closely related child objects within the schema of a parent record - in your example you might include Questions as children of a Survey and store them in one record, unlike in relational modelling where you would put these in separate tables.