User Profile
avishek_g
Frequent Visitor
Joined 3 years ago
User Widgets
Contributions
linked objects (Dataflow tables) transformation
Create and Transform a Power BI Dataflow Using Other Power BI Dataflow Go to Power BI Service and then to your Workspace Click New Item and then choose Dataflow and click on Add new table and the select Power BI dataflow (Legacy) It will ask you to validate or change your authentication kind. By default it should have Power BI - > Now click Next Once inside, you should be able to enter an interface where you'll find all the Power BI dataflows you have access to. Expand them and choose the desired tables from under them and proceed to transform data This will open the desired table in a Power Query Editor. However you will soon discover that you're not able to modify the table as the source dataflow appears into your dataflow as a Linked table. Power BI wouldn't let you modify linked table to maintain "single source of the truth". What you can do is create another table as a reference to this linked table and do you transformation on this reference table. Finally don't forget to refresh this reference table before consumption and set-up scheduled refresh on this the refrence tableRe: report development end to end process
Hello Your process flow is correct. Below are also some of the other points I want to highlight: The development lifecycle is divided into several stages to ensure thorough planning, development, and deployment: Requirement Elicitation Workshop: Gather initial requirements from stakeholders. Requirement Analysis and Documentation: Analyze and document requirements, followed by data profiling and sign-off. Wireframe Creation: Develop low-fidelity visual representations of the solution. Development: Build the Minimum Viable Product (MVP) and iterate based on feedback. Deployment: Finalize and deploy the product after thorough testing. Following activites enable the infrastructure for starting and continuing with the development: 1. Infrastructure Setup Power BI Workspace Creation: workspace creation with specific details such as workspace names and user permissions. MS Teams and SharePoint: Create an MS Teams group for internal stakeholders and set up a structured folder system for requirement documentation, development documentation, data sources, and PBIX archives. Data Source Service Accounts: Request read-only access to Data Warehouse and other data sources and set up Power BI gateways for any on-prem servers used as a source. Power Automate/App Credentials: Develop workflows applicable for data refresh if Power BI's native scheduling is not suitable for the desired refresh cadance. Set up Azure DevOps/GitHub Repository: Set up Azure DevOps or GitHub repository to be used for version controlling and cloning them them in the respective developers' local dirctories. Set-up Azure DevOps/Jira Board for Project Tracking: Setting up a Canban or a Scrum board for daily project activity tracking. 2. Agile Development Cycle The framework follows an agile development cycle, emphasizing iterative development, continuous feedback, and regular updates. Key components include: Sprint Backlog: Maintain a backlog of tasks and features for each sprint. Business Specifications and Development Documentation: Document business requirements and development processes. Testing and Feedback: Conduct regular testing and incorporate user feedback. 3. Table Naming Conventions To maintain consistency and clarity, the framework specifies detailed naming conventions for tables and measures: Staging Tables: Prefix with STAGING_ followed by the table content and source abbreviation. Fact and Dimension Tables: Use FACT_ and DIM_ prefixes for fact and dimension tables, respectively. Calculated Tables: Prefix with CT_ followed by the table content. Measures: Use descriptive names indicating the KPI, calculation, and usage. 4. Linting Standards The framework enforces strict linting standards for writing DAX expressions: Naming Conventions: Follow a consistent naming pattern for measures and variables. Comments and Annotations: Include relevant comments and break down nested DAX into readable lines. Folder Structure: Organize measures into appropriate folders within measure tables. 5. Data Model and Design Standards Each KPI or functionality should have its own ER diagram, illustrating the flow of filter context. The design template and color palette adhere to corporate standards, ensuring a consistent and professional look. 6. Documentation Comprehensive documentation is crucial for maintaining clarity and facilitating future updates. Key documents include: Requirement Elicitation Document: Captures initial requirements and is signed off before development. Data Profiling Document: Details the schema, keys, granularity, and other data characteristics. Wireframe: Provides a visual representation of the solution. Product and Sprint Backlog: Lists development tasks and features. Data Ingestion Document: Describes the data ingestion strategy. User Guides: Provide instructions for using the product. Maintanence Document: Documenting steps for activities to be continued during product's lifetime such as adding, removing users etc. Test Scenarios and Results: Document test cases and outcomes. Specimen of Requirement Elicitaiton Document: Specimen of Data Profile Doc:Re: Hide/Unhide Slicer based on another slicer values
There is no off-the-shelf way in Power BI to control the visibility of a slicer's values dynamically (No *fx* button next to the value font color selection). However, you can show or hide one slicer (slicer 2) based on the selected value of another slicer (slicer 1) by applying the below work around. It's a solution using bookmarks: Scenario: I have 2 slicers, Slicer 1, called "Currency" and Slicer 2 called " Rate". Slicer 1 has 2 options " Global" and "Local". Slicer 2 has 2 options "Fixed" and "Variable" Business Requirement: The need is to give the user the option to select between Fixed and Variable rates when the user selects Global currency. When the user selects Local currency, the 2nd slicer is irrelevant. Hence it should be hidden. Solution: Create 2 bookmarks and name them "ShowRate" and "HideRate" insert 2 completely transparent rectangles and place them on top of each radio button/switch of "Globa" and "Local" option of slicer 1: Currency Update the "ShowRate" bookmark - while selecting Rate Slicer - visible, currency slicer (selected to global) - visible. Then update "HideRate" bookmark - while selcting Rate Slicer - imvisible, Curreny Slicer (toggled to Local) - Visible Tick marked to "Data" and "Selected Visuals" for both updation. Result: Now upon clicking on the Global button you can show the Rate Slicer While selecting the Local option in Currency will hide the Rate slicer Point to not that when the user is clicking on the Currency sliceer, it's appearing that they are clicking on the slicer radio button but actually they are clicking two imvisible bookmarks that hide or show the other visual.Re: Hide slicer based on other slicer selections
There is no off-the-shelf way in Power BI to control the visibility of a slicer's values dynamically (No *fx* button next to the value font color selection). However, you can show or hide one slicer (slicer 2) based on the selected value of another slicer (slicer 1) by applying the below work around. It's a solution using bookmarks: Scenario: I have 2 slicers, Slicer 1, called "Currency" and Slicer 2 called " Rate". Slicer 1 has 2 options " Global" and "Local". Slicer 2 has 2 options "Fixed" and "Variable" Business Requirement: The need is to give the user the option to select between Fixed and Variable rates when the user selects Global currency. When the user selects Local currency, the 2nd slicer is irrelevant. Hence it should be hidden. Solution: Create 2 bookmarks and name them "ShowRate" and "HideRate" insert 2 completely transparent rectangles and place them on top of each radio button/switch of "Globa" and "Local" option of slicer 1: Currency Update the "ShowRate" bookmark - while selecting Rate Slicer - visible, currency slicer (selected to global) - visible. Then update "HideRate" bookmark - while selcting Rate Slicer - imvisible, Curreny Slicer (toggled to Local) - Visible Tick marked to "Data" and "Selected Visuals" for both updation. Result: Now upon clicking on the Global button you can show the Rate Slicer While selecting the Local option in Currency will hide the Rate slicer Point to not that when the user is clicking on the Currency sliceer, it's appearing that they are clicking on the slicer radio button but actually they are clicking two imvisible bookmarks that hide or show the other visual.
