Edit forms not pulling in data to cards

[tjohn106]

I am working on a modified form that interacts with a SharePoint list to log and update information.

So far I have the new form working exactly as I want it, but I am struggling to regain the functionality to edit data entries after some heavy modifications to some of the cards.

My application uses a search gallery, MasterSearch, to find an entry from the SharePoint list.

I can then click the details to open up more information about the entry (relatively similar to the default data view).

On this page I have a icon with the following code to open up the editable form:

EditForm(EditForm1);Navigate(EditScreen1, ScreenTransition.None)

It will then pull the form up but no data will be in any of the cards on the form.

Note that on this same page I am able to bring in a display form and have it display data with the Item listed as MasterSearch.Selected (same as the item on the edit form) so I think it is finding the entry just fine.

Please let me know any thoughts that you might have and I am sure that you would need more information to help me, but I am just unsure of what is needed. 

Thanks in advance!

[RandyHayes]

@tjohn106 

Does your Item property actually have a record in it when you go into edit mode?

I believe you are stating that it is based on MasterSearch.Selected 

I would consider the following instead.  

- Change the OnSelect action formula that takes you to the EditForm from MasterSearch to  include the following:  Set(glbCurrentRecord, ThisItem)

- Change the Item property of your EditForm to glbCurrentRecord

- Change your OnSuccess action of the form to: Set(glbCurrentRecord, Self.LastSubmit)

See how that works out.

I hope this is helpful for you.

[tjohn106]

@RandyHayes 

Thanks for providing some input!

I tried your proposed solution, but the form still did not load an entry.

I confirmed through the variable screen that a record did get loaded into glbCurrentRecord so whether or not it had a record loaded before, I feel rather confident it does now.

The only modification that I had to make was setting glbCurrentRecord on the MasterSearch Gallery Selection (which opens up a detail form) instead of on the edit form open button which is on that detail form screen. When I had tried to place it on the button there was an error (I think it couldn't find ThisItem but I am not sure).

Properties from Search Gallery:

Properties from EditForm:

[tjohn106]

So I ended up figuring out what was going on. 

I had used a collection to get around some delegation errors, but the record that was being referenced was from this collection. I expanded the number of columns to include all columns that I cared about and now my form fills.

@RandyHayes thanks again for taking a look at this and sorry for sending you on a wild goose chase.

[RandyHayes]

@tjohn106 

Yes, I would reconsider your need to create collections and instead work around the delegation issue to reduce the overhead and performance hits on your app (plus the extra work you would need to do).

It's much easier to work around delegation than it is to jump through hoops in your app to try and craft your own record schemas and in-memory databases.

[tjohn106]

@RandyHayes 

If you cannot tell I am rather new to PowerApps coming from a more Python/Matlab background and am just starting to learn.

Do you have a suggestion for how to get around the delegation warnings?

My goal that ran me into delegation issues is having a searchable list for objects that I can filter based on a unique identifier. However, whenever I used the lookup, filter, or other functions to sort through that SharePoint list I received a delegation warning. 

The only way that I found around it is to pull that list into a collection.

[RandyHayes]

@tjohn106 

Tell me more about your formulas that you received the delegation warnings on.  Perhaps I can provide some guidance on how to avoid them.

[tjohn106]

@RandyHayes 

Note that AttributeMasterCollection is a collection built from:

ClearCollect(AttributeMasterCollection, 'Attribute Master Log')

Here are the two formulas that I have used. The collection does not give me delegation issue while the list does. I have used other variant of the filter formula and lookup formula, but I did not keep a record of them.

//SortByColumns(Filter(AttributeMasterCollection,QuickMasterSearch.Text in Master_x0020_Number),"Master_x0020_Number", If(SortDescending1, Descending, Ascending))
SortByColumns(Filter('Attribute Master Log',QuickMasterSearch.Text in Master_x0020_Number),"Master_x0020_Number", If(SortDescending1, Descending, Ascending))

QuickMasterSearch is a text input that allows the user to filter for results. Here is a screenshot of the main search screen in case that helps contextualize what is going on.

[RandyHayes]

@tjohn106 

How many records do you have in your 'Attribute Master Log'?

Is there any narrowing of the records you can do?  In other words, you're trying to do the in operator against all records, is it relevant to all records?  Are there certain records that would not be relevant to the search?  Things like a record that would never apply to the app - such as it is "closed" or not related in some way?

[tjohn106]

I am using this to be a database for all of our controlled objects (masters). I could feasibly create other filters, but those filters could still represent a couple hundred values by the time all the data is input.

A lot of the people using this app I do not expect to be very technically gifted, so I am trying to limit the amount of buttons they would have to press in order to find the record they are looking for.