on
RE:
As an enterprise application developer we wanted to have SSO to the Power BI Service from our product to Power BI Service using our identity provider (which is used by our application to managed authentication). To achieve this we have set up a custom SAML identity provider for a workforce tenant in Entra ID.We have identified that we need to invite guests to the workforce tenant and configure our Identity Provider as a custom provider in Entra ID. The workforce tenant type is the only tenant type where Power BI Service is available for SSO, so we registered the provider there. Custom identity providers use domains to bind users to specific providers. Invited guest users that come from our application can have emails from any domain, as it is supported by our Identity service. Thus, we cannot specify only a single federation domain for this provider. Entra ID provider configuration requires specifying every single domain used with the provider. After following documentation and configuration steps the option to log in with a custom provider never appears on the Power BI Service login screen, even when using the tenanted URL (the URL available on Power BI Service to direct users to specific Power BI Service tenant) or using ‘Login with organization’ form (where we specify the custom identity provider domain). Can we have a way to configure custom SAML identity provider in Entra ID to be the only and default provider for all invited guest users? Can we have a way to configure custom OIDC identity provider in Entra ID for a workforce tenant? OIDC is preferred and widespread protocol today.Can we have a way to directly configure Power BI Service with custom identity provider (SAML/OIDC) for SSO, as it is available today in Microsoft Power Pages?
RE:
Please implement this Microsoft.
RE:
We also need attachments to be attached on our Production Order
RE:
Hi, has this been resolve or implement? We have the same issue which last row/line of the exported excel will display "No filters applied" or with "Applied filters: xxxxxxxxxxx". We need to impose a manual step to remove them.
RE:
The ability to run simulated depreciation for a nominated date range with similar parameters to depreciation proposals and report the results by month for the nominated date range would be very useful for budgeting / forecasting.How soon can this happen?
RE:
The 20 bookmark limit is so strange. Microsoft can you please raise the limit or remove?
RE:
Please add an option to retire a job - or mark it as inactive. Retired jobs should not be available in the list of jobs a new position can reference. Scenario: a customer has re-structured their jobs and titles and no longer wants to make use of the original jobs. All workers have be assigned new positions that reference the new jobs. The old jobs are referenced in previous positions of the workers and therefore cannot - and should not - be deleted. But it shouldn't be possible to reference them in any new positions. It is not enough to update the job description to 'DO NOT USE' - as many, both HR persons as well as managers requesting new positions - do not use the drop down, but simply enter the job id they remember.
RE:
There should be a way to edit/change job titles. There are few job titles with typo which is been used in positions, which we want to change or atleast apend with "Do not use". At the moment there is no standard provision for this in the system. Please provide this functionality so that the old titles can stay as it is after making the change.
RE:
As we have in org. management active positions and all positions it would be really useful to have the same lists for the jobs. In the job list, there is a button - manage changes, where we have a possibility to set an expiration date. However, expired jobs are still visible in the list and also they come up when we link a position with the job. So what is the purpose of having an expiration date in jobs?
Since the organizational needs are evolving, from time to time we add new jobs and eliminate old ones. Currently, the only way to hide expired jobs is to delete them from the list which also requires deleting the history from position details. I believe it is not the correct way to manage historical data.
My suggestion is to have two lists: active jobs and all jobs (where we will find expired jobs as well). So when the user will assign the job to the position an active list will be showing up.
Furthermore, if the inactive job is still needed then from manage changes a new time period will be set which will make a job active again.
I am sure this feature will enrich the job management process and make it easier to maintain jobs' data. Besides this feature will enable to keep the historical data in the position details.