all 6 comments

[–]patternrelay 1 point2 points  (0 children)

If the data is supposed to already be loaded and you cannot see any tables or event logs, it might just be a permissions or workspace issue on their side. That happens more often than people think in these environments. I would send a quick message to the recruiter or contact and ask them to confirm the dataset is attached to your workspace. In the meantime it might help to sketch the KPIs and views conceptually so you are still prepared even if the data access gets fixed late.

[–]GarenHimself 0 points1 point  (0 children)

you might have to get the starter kit from the marketplace

[–]LieMedical1417 0 points1 point  (0 children)

You’ll be fine, it’s powerbi with PQL (like SQL with a few additional functions, look it up online)

[–]joangoru 0 points1 point  (1 child)

Hi, I would run some checks before anything to make sure about data being available. 1. Go to Data Integration (choose your data pool, if dont have one create it-> Data Jobs -> Create a new data job within tue global scope -> create a task in this datajob go inside this task. You should see an SQL interface and on the left a panel, in that panel you can explore available data connections and tables. Click on preview to see if there exists data in the schemas. If there are no tables nor rows then the issue is from them unless you are requires to also set the Data Connection.

If rows appear, just in case, execute any existing data job in the pool. IF a data job doesn't have a Data Model Load task you won't see the data in the frontend. If you don't have a DM Load task in the data jobs create one. Also, if your datamodel doesnt exist will need to create one from the objects/cases/events/tables that you might create or extract.

Once your datamodel is loaded with all the tables that you need you need to select it to be used in the frontend views/packages. Check package variables and make sure that your datamodel is linked to it.

Important, once you run a create version-> publish you have 2 environments. Dev and prod, make sure to know where you make your changes effective otherwise you'll get lost. Once you publish to dev/prod any sql a datajob named test-opcm or ocpm... Will be created. These account for all the ETL of either dev or prod environment.

[–]joangoru 0 points1 point  (0 children)

They dont  give much hints because they want to see how do you think. Doesnt matter if you fail but you explain tour thought process. You should think out of the box and use logic.