Power Bi Points To Keep in Resume
Power Bi Points To Keep in Resume
======
Power BI Developer Responsibilities in One Project
===================================================================================
======
14.Created dashboard using report tiles, books marks, and other actions.
15. Specified users to access reports at data set row level security
16. Specified Scheduled refresh for the report based on customer instructions
17.Shared and Subscribed the the reports, dashboards ad per customer requirement.
18. Generated alerts when customer required point reached.
19. We answered for the customer’s reviews and notifications.
===================================================================================
======
Power BI Admin Responsibilities in One Project [usually in very large
organzations]
===================================================================================
======
Experience in Power BI Administration portal and performed below tasks
o Managing workspaces
o Publish Reports and dashboards
o Monitoring and troubleshooting data connection and data refresh
o User administration like Create and manage users and groups, assigning roles
o Enable and disable Power BI features
o Report on usage and performance
o Review and manage auditing
o Manage workloads
o Performance issue analysis and fix
o Manage Power BI connections like gateway's to on-premise Database and connectors
o Manage subscriptions
Exposure to databases such as SQL Server/SQL DWH
Assist in designing and development of technical architecture and requirements
===================================================================================
======
Power BI Support Responsibilities in One Project
===================================================================================
======
a) They work in one support tool( Servicenow, Assure Service Desk), where they find
production issues (live system / report issues)
b) The issues are entered by the customer team in to the tool
c) The issues may be incidents (one time occured) or problem tickets (frequently
occured issue raised as problem for detailed diagnosis) or performance issues
Ex: Incidents
Problem Tickets
Performance issues
d) There are multiple production levels [L1 (high), L2, L3, L4 (low)], and the
severity in each level is P1(high: 2-4 hrs), p2 (8-10 hrs), P3, P4 (low)
L1 incidents: P1,P2,P3,P4
L2 Incidents: P1,P2,P3,P4
L3 Incidents: P1,P2,P3,P4
L4 Incidents: P1,P2,P3,P4
Resolution:
a) Verify at report level the issue or going to Audit or Log files, monitor the
issue area
b) Implement the change at near production (UAT / Integration etc.), test it, peer
review it and go for approvals
c) Implement the change at production.
===================================================================================
====
How do we get the documents in realtime?
===================================================================================
====
Project 1 culture:
=================
Developer Design: Creating a multi page report which is controlled by single page
dashboard
Day-Day responsibilities:
In this project working with the pending tasks.
a) Kick off meeting: Project Initiation meeting: Here development team introduced
to customer team [other technical team]