Sharepoint just stuck at Getting your data

(0) Share

Report

Posted on by tmw900

I have created a form using a Sharepoint list. When I click into the form in SP, it just hangs up at Getting your data.

I've tried the following steps:

1) My OnSuccess value is ResetForm(SharePointForm1); RequestHide()

2) I switched the form default property from Edit to New.

3) I tried to add If(IsBlank(LookUp('Intake Form', ID = SharePointIntegration.SelectedListItemID)), First('Intake Form'), LookUp('Intake Form', ID = SharePointIntegration.SelectedListItemID)) to the Item value but receive the following message. "Delegation warning. The highlighted part of this formula might not work correctly on large data sets. "First" operation is not supported by this connector."

Please help.

Categories:

Building Power Apps

I have the same question (0)

All responses (11)

Answers (1)

WarrenBelz 153,051 Most Valuable Professional on at

Like (1)

Report
Hi @tmw900 ,
The OnSuccess should not matter as it only triggers after a form is submitted
Put the default to Edit or View - the built-in controls (OnView, OnEdit, OnNew) will take care of all of that.
With the Delegation error, put the Form Item to
SharePointIntegration.Selected

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Was this reply helpful? Yes No
v-siky-msft on at

Like (1)

Report
Hi @tmw900 ,

The issue is caused by Items property of Form.

What is 'Intake Form'? Is it the form you are editing and customizing?

If so, please modify the code as follows.

If(IsBlank(SharePointIntegration.Selected)|| IsEmpty(SharePointIntegration.Selected), First([@'Intake Form']),SharePointIntegration.Selected)

Hope this helps.

Sik

Was this reply helpful? Yes No
WarrenBelz 153,051 Most Valuable Professional on at

Like (0)

Report

Thanks @v-siky-msft ,
I actually had a delegation error yesterday on that standard code and needed to change it to what I posted. It should not happen I know, but it did and I have seen a couple of other posts with the same issue.

Was this reply helpful? Yes No
tmw900 9 on at

Like (0)

Report

Hi @WarrenBelz,

Thank you for your reply. I made your suggested changes and it still hangs up with the 'Getting your data'.

One thing to note, my labels will display on the Getting your data screen but none of the form fields. Any other thoughts?

Thanks,

Was this reply helpful? Yes No
tmw900 9 on at

Like (0)

Report

Hi @v-siky-msft,

Intake Form is the name of my datasource. I added the code you provided in the Item field and I still get the same Delegation warning. My form name is SharePointForm1. Does the order in the tree view matter? I have SharePointForm1 at the top and then labels and buttons below.

Tom

Was this reply helpful? Yes No
Verified answer

v-siky-msft on at

Like (5)

Report
Hi @tmw900 ,

I have tried, but I can't reproduce your issue, there is no delegation warning in Items property.

Here is an alternative workaround, try to modify the Items property as follows.

LookUp(postcode,ID=SharePointIntegration.SelectedListItemID)

If it still shows "Getting your data", please consider deleting the powerapps form in List Setting - Form Setting - Delete custom form, and then re-create one to see if the warning is gone.

Hope this helps.

Sik

Was this reply helpful? Yes No
tmw900 9 on at

Like (0)

Report

Hi @v-siky-msft,

That worked! Thank you very much.

Tom

Was this reply helpful? Yes No
KevinColeMCM 36 on at

Like (10)

Report

Deleting your form and recreating it is a poor solution. Especially when it takes 8 hours to make the dang form.

Was this reply helpful? Yes No
darrellwinston 7 on at

Like (2)

Report

Exactly. It takes forever because of the STUPID User Interface design. I have NEVER seen an IDE change Properties on another Control, because I am editing a separate Control. So deleting the the Form is a Terrible solution...but the way this application is made, I wouldn't be surprised if that is the only solution... Sorry about my venting here.

Was this reply helpful? Yes No
mkortink 8 on at

Like (0)

Report
I have had this problem twice, and if you search so have many others, I will give my answer here and hope other can find it.

What happens is the SharePointIntegration connector becomes corrupted and no longer works properly. How, I think if you make even minor changes to the list structure it can screw up SharePointIntegration which seems to have the previous list structure embedded in it somehow.

While SharePointIntegration.SelectedListItemID still gets set correctly SharePointIntegration.Selected is empty. Sometimes using LookUp(YourList,ID=SharePointIntegration.SelectedListItemID) instead of SharePointIntegration.Selected seems to work, but it never worked for me.

My solution does require some effort, but it is better than starting from scratch. I will outline it here, you can work out the details.
You have a list I will call ListA and it has a custom form I will call screenA.
Create a separate new canvas PowerApp I will call appB and connect it to the listA as a datasource. Make sure all the names are the same.
Create a blank screen in appB called screenB.
Open the custom form screenA from listA in PowerApps.
Press Ctrl-A then ctrl-C to select everything on screenA and copy it all to the clipboard.
Go to appB, select screenB, and press Ctrl-V to paste everything onto the screen. This is your backup screen, it will probably have some errors due to SharePointIntegration not existing in appB, and the formatting might be messed up, but ignore these errors.
Look for errors in appB that relate to variables and collections and other stuff outside of sreenB, make careful notes, you will need to recreate these later.
Go back to the list, open it settings, select form settings, and switch to using the default SharePoint form making sure you delete the custom form. Thats right, get rid of it completely!
Now to make sure, go to the list and add/edit some items to make sure the default form is being used.
Now create a custom form again, SharePoint will open PowerApps and give you a default screen to start customising which I will call screenC.
Make a minor visible change to screenC, go back to the list, test screenC works (you will know you are getting screenC because you can see the minor change. This proves SharePointIntegration is working again.
From the list open the custom form in PowerApps again.
Now select all, copy and paste (Ctrl-A, ctrl-C, ctrl-V) screenB from the backup to screenC. All the controls should hook up because SharePointIntegration and the same datasource are in the custom form app.
You may still have errors. Use the careful notes you took in step 7 to resolve these.

Was this reply helpful? Yes No