Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check Space Availability and Provisioning Request approval flows #107

Open
PrinsGeryha opened this issue Oct 11, 2024 · 4 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@PrinsGeryha
Copy link
Contributor

Description

Check Space Availability flow is not able to add the correct SharePoint site, it lists Microsoft Contoso's site which has nothing to do with my installation. See image below. For now, I need to share the flow with every user who needs access.

image

Provisioning Request Approval flow is disabled after importing it from managed file. Should be a step in the documentation for enabling it or have it enabled by default.

Steps to reproduce

  1. Follow documentation
  2. get to the import ProvisionAssist_2_0_0_2_managed.zip into power apps step.
  3. See issue

Expected results

Should be able to choose correct sharepoint site and list in Check Space Availability.

Provisioning Request Approval flow should be enabled by default or added into the deployment guide.

Actual Results

Check Space Availability flow is not able to add the correct SharePoint site, it lists Microsoft Contoso's site which has nothing to do with my installation. See image below. For now, I need to share the flow with every user who needs access.

image

Provisioning Request Approval flow is disabled after importing it from managed file. Should be a step in the documentation for enabling it or have it enabled by default.

Solution component

Power Automate Flows

Operating system (environment)

Windows

Additional Info

No response

@PrinsGeryha PrinsGeryha added the bug Something isn't working label Oct 11, 2024
@swallace74
Copy link

I had the same issue. I couldn't work out how to resolve it from PowerAutomate so instead I extracted the provisionassist_1_1_0_3_managed.zip file (from the "..Source\Power Apps" folder - the version number may be different) and opened the CheckSpaceAvailability- Json file. In here find the "Provision Assist SPO Site (msftprov_ProvisionAssistSPOSite) section and change the default value to the URL of your ProvisionAssist SharePoint site. Get the list ID of the Provisioning Requests list by browsing to the list, click the settings cog and choose List Settings. Copy the string from the end of the URL (after "List=..."). Remove %7B from the start and the %7D from the end to get the list ID and put this into the defaultValue attribute in the "Provisioning Requests List (msftprov_ProvisioningRequestsList)" section in the json file. Save the json file and then zip all the files up. Save the file to the original location, overwriting the existing file.
You'll then need to import the solution again as per (https://github.com/pnp/provision-assist-m365/blob/main/Deployment-guide.md#step-5-deploy-power-apps-solution)

@swallace74
Copy link

And I agree on your point about the Provisioning Request Approval flow

@alexc-MSFT
Copy link
Collaborator

Thanks @PrinsGeryha and @swallace74 for raising these issues. For the run only piece, this seems to be a Power Apps product bug from what I can tell, I'm doing some research as we speak and will keep you updated, the default value should not affect the ability to use that run only drop down and it shouldn't only show a site from the wrong tenant either (or at least it didn't use to), watch this space.

@alexc-MSFT alexc-MSFT self-assigned this Oct 11, 2024
@alexc-MSFT
Copy link
Collaborator

@PrinsGeryha @swallace74 update on this, editing the Check Space Availability flow and saving it (without making changes) fixes the 'run as' drop downs. This is easier than editing the JSON files which obviously should not be required.

It's clearly a product bug as the environment I export from is set to exclude the default values.

I've updated the documentation temporarily with steps on how to edit and save, and I've also added a part about turning on the approval flow.

I'll keep the issue open while I take up the bug with the Product Group.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants