I am trying to se the visibility of a Power Apps container based on a yes/no entry in a SharePoint List.
I tried:
If(SharePointList.ColName,"Yes",true,false)
But no joy.
Related
This is a power BI Desktop query.
I've been trying to add a custom map in shape map.
The custom map I'm trying to use is the world-countries-san-anartica.json found here: https://github.com/deldersveld/topojson
And the dataset am working on is the Sovereign states and dependencies by population table in https://en.wikipedia.org/wiki/List_of_countries_and_dependencies_by_population
When I click Format -> Shape -> Add Map and upload the custom map, I still see the USA: states (default) map in my dashboard and not the custom map.
How would I fix this?
Thanks!
I am new in power bi. I am using SQL connection for data load in power bi.
I created the report in Dev environment. But I want to use the same report in all environment(dev/test/uat/prod).
Question: Is it possible to switch the connection via button click in dashboard?
You'll have to use a parameter to select the connection and store the report in template format - *.pbit. Then you can easily create different versions of the report from the template by specifying the according parameter setting.
The only way to use a slicer for changing the environment would be to load the data from all different environments into the model first - which is clearly not recommended.
Power BI offers Deployment Pipelines for this purpose. This tool will allow you to create 3 workspaces for dev, test and production stages. Then you can deploy from one stage to another by clicking a button in Power BI Service or using the REST API. In the pipeline you can define rules for dataset and parameters, which can be used to automatically change the datasource when deploying to the next stage, i.e. to change the datasource from your dev database to the test database, or from test database to production one.
You can also implement similar functionality using the API. See for example this answer.
Its tricky question.
Try with above answers, if those not work try with these approach.
I don't think for the moment they didn't implement solution for that.
From my experience I had to create 3 dashboards and gateways to dev, test and prod dashboard.
If your dev,test,prod database column names are same you just copy past your dashboard and rename it according to that.
Then go to change data source and add new test env host and change schema to test env.
If you get few errors you have to resolve , check column names, host and finally you have to sync your data.
You can use same approach for the prod env .
once you publish, you can point to gateway for dev,test or prod environment.
Note: Establish gateway on your server.
My initial requirements was to create a PowerApp that's integrated with Power BI using one of the columns (say col1) from tables used in Power BI report. I implemented this and published the app.
Now, the requirements have changed and the request is for an additional column (say col2) in the same app. How can I add an additional new field that can somehow show under PowerBIIntegration.Data.col2?
I didn't find any documentation or reference for the same. In past, I have built PowerApps with multiple columns but not sure how to add new column to existing PowerApps when integrated with Power BI.
I had the same issue, what you need to do is edit the power app from the PowerBI file or published version too.
Steps:
Open the PowerBI file or the published file with clicking on edit
Select your existing PowerApp visual
Add the new columns by checking the new column check boxes per usual
Then hover over the PowerApp Visual and click on on the three dots that appear in the top right of the powerApp visual, and select Edit,
This will launch PowerApp studio page so you can edit the app
Using this method will also connect your app to the live data set from the PowerBIIntegration data set.
source text:
"If you change the data fields associated with the visual, you will need to edit the app from Power BI service to make sure that the changes are propagated to PowerApps. You will observe unexpected behavior if the app is not edited from Power BI service to make sure that the new fields from Power BI reflect in the app."
https://powerapps.microsoft.com/et-ee/blog/powerbi-powerapps-visual/
I have the following structure in my Sharepoint:
Parent Site (site collection)
Project A (subsite)
Orders List
Project B (subsite)
Orders List
Project C (subsite)
Orders List
Orders List is the same for all subsites.
I'd like to create a single workflow that will work for all Orders List.
If I create a workflow for each list on each subsite, maintenance will be hard.. Will have to update all workflows separately once one is changed.
I've looked into workflow attached to content types but it doesn't work in SP 2013 Workflow.
What is the best way I can do this? Maybe create a workflow on the parent site that works for all subsites calling same list.
I have to migrate some legacy data from stand-alone sql server database to sharepoint list.
I'm going to use programmatic approach and write a code that communicates with sharepoint list asmx web service.
Are there some "data transformation wizards" to simplify such a task or a better approach to port legacy data from sql server database to sharepoint list?
Thank you in advance!
Being one time operation, I would not worrry about Best Practice but would consider what's the fastest way to do it.
You can use Excel 2010 (I have not tested it with Excel 2007) export data to Sharepoint 2010. Here are the high level steps:
Import data from SQL Server using DATA Tab in the ribbon
Excel would automatically create a TABLE
Now you can prepare the data for Export to Sharepoint. Here, you can remove unwanted columns, add new columns remove unwanted rows, arrange columns etc.
While being in the Table, access the "Export Table To Sharepoint List" functionality to publish you data to Sharepoint. More information about this is available at: http://office.microsoft.com/en-gb/excel-help/export-an-excel-table-to-a-sharepoint-list-HA010131472.aspx
It is quick! but let;s be aware of the limitations:
1. It cannot publish data to a list which already exists
2. It will not create a content type for the exported list. The columns are directly attached to the list.
If you want greater control over the migration, programming may be the way to go unless someone has a better idea in this great forum!