No Data Source Provided/No Item to Display on Main screen that does not contain a form

[HawkinsGabriel]

I have created an app that contains multiple screens with multiple forms. I can preview the app without issue when editing it, but when I try to run the app, I get a screen with an empty form with a check box that starts saying "No Data Source Provided" which quickly changes to "No Item To Display." The starting screen is just a navigation page. It has no forms, on controls to navigate to other screens that do have forms. The datasource connections look okay for all of the forms on other screens, and the Item property for each of the forms is correctly filled out with the "Defaults(datasource)" information, as is the data source property. The exception would be forms that link to galleries, but those galleries are correctly linked to the correct datasources. Any assistance would be greatly appreciated, and I woul dhappy to provide whatever information would make diagnosing this issue easier.

[v-xida-msft]

Hi @HawkinsGabriel,

Could you please share a bit more about the issue within your app?

I have made a test on my side, and don't have the issue that you mentioned. Based on the error message that you mentioned, it seems to tell that there is something wrong with the data source your Edit form connected to.

Please check if you have specified proper data source within the DataSource property of the Edit form control.

In addition, I think there may have something issue with the formula you provided within the Item property of the Edit form. Please modify the formula within the Item property of the Edit form to following:

Gallery1.Selected  /* <-- Gallery1 represents the Gallery control the Edit form relates/links to */

Note: If you don't set a default value for any field in your data source, the Defaults(datasource) formula would return a empty record.

More details about Defaults function in PowerApps, please check the following article:

Defaults function

[HawkinsGabriel]

The Item property for the edit forms that link to galleries are set up as you describe.

So my problem is that the only way I can run the app is to open it in edit mode and preview it.  If I try to just open the app normally I get the error messages I describe.

Here is the set up for the app - It's a tool used to add employees to project numbers so that they can log time appropriately.  The only data sources linked to are -

1. An Excel table (PN_Requests) containing the assignment requests submitted by employees through the app.  So it starts blank and has rows added as employees make submissions.
2. An Excel table containing a single project number for each of our clients.  This table is made up of rows for each client/project number, and it is not edited, only referenced.
3. An Excel table (ProjTeamPNs) containing multiple project numbers for each of our clients, broken down for specific tasks.  This table is made up of rows for each task for each client and the corresponding project number.  It is not edited, only referenced.

The app's make up breaks down like this -

• The main screen just contains a number of links to other screens that contain various forms and galleries.  It has no galleries or forms of it's own.
• The second screen (linked to from the main screen) contains a single edit form (Item property - Defaults(PN_Requests)) that adds a single row to Data Source #1.  There is also a link back to the first screen.
• The third screen is designed to add multiple associates to a single project number.  It contains two edit forms: one to enter a single project number, and one to enter up to 10 employees.  Both have the "Defaults(PN_Requests)" Item property.  A submit control pulls information from both edit forms to add multiple rows (to Data Source #1) for however many employees are entered into the second edit form.  There is also a link back to the first screen.
• The second edit form (where you enter the multiple employees) is contained in a data card which is contained in a canvas, so that whoever is using the app can scroll.
• The fourth screen is almost exactly like the third, except it is designed to add a single employee to multiple project numbers.  So it also has 2 edit forms, one two enter a single employee, and one to add up to 10 project numbers.  Both have the "Defaults(PN_Requests)" Item property.  A submit control pulls information from both edit forms to add multiple rows (to Data Source #1) for how ever many project numbers are entered into the second edit form.  There is also a link back to the first screen.
• The second edit form (where you enter the multiple project numbers) is contained in a data card which is contained in a canvas, so that whoever is using the app can scroll.
• The fifth screen contains a control to enter in information for any large/strange requests, which would be emailed to a support inbox.  There are no forms or galleries.  There is also a link back to the first screen.
• The sixth screen contains 3 links to 3 tools for use by those people who actually complete the assignments requested in the above screens.  There is also a link back to the first screen.
• The seventh screen is the first tool referenced in the sixth screen.  It contains a gallery that pulls in rows from Data Source #1 that have not been completed (Items property - Filter(PN_Requests, IsBlank(Status)), and an edit form (IncAssignGal.Selected) that displays all of the information for whichever row/record is selected in the gallery and a control where you can enter notes.  You can either submit the form to change a row/record to a completed status or a pending status.  There is also a link back to the sixth screen.
• The eighth screen is the second tool referenced in the sixth screen.  It contains a gallery that pulls in rows from Data Source #1 that have been given a pending status (Items property - Filter(PN_Requests, Status= "Pending")), and an edit form (PendAssignGal.Selected) that displays all of the information for whichever row/record is selected in the gallery and a control where you can enter notes.  You can submit the form to change a row/record to a completed status.  There is also a link back to the sixth screen.
• The ninth screen is the third tool referenced in the sixth screen.  It contains a gallery that pulls in rows from Data Source #1 that have been given a completed status (Items property - Filter(PN_Requests, Status= "Complete")), and an edit form (CompAssignGal.Selected) that displays all of the information for whichever row/record is selected in the gallery and a control where you can enter notes.  You can submit the form to change a row/record to a pending status.  There is also a link back to the sixth screen.
• The tenth screen has a gallery (Items property – (ProjTeamPNs) displaying rows/records from Data Source #3 and 2 edit forms: an edit form (ProJTeamPNsGal.Selected) that displays information from the row/record selected in the aforementioned gallery, and an edit form (Defaults(PN_Requests)) for inputting employee information to add a row/record for an assignment request.  An employee could select a row/record for a particular task for a particular client in the gallery (from Data Source #3) and add a row to Date Source #1 using the information from the first edit form (referencing the gallery displaying info from Data Source #3) and information about themselves that they enter in the second edit form (whose data source is Data Source #1).  There is also a link back to the twelfth screen.
• The eleventh screen is exactly like the tenth screen, except the gallery references Data Source #2 information.  So, it has the gallery (Items property - (NonProjTeamPNs)), the first edit form (NonProJTeamPNsGal.Selected) displaying data for the row/record selected in the aforementioned gallery, and the second edit form (Defaults(PN_Requests)) for inputting employee information.  This second form again uses Data Source #1 as its data source.  There is also a link back to the twelfth screen.
• The twelfth screen is another screen that just contains links to other screens.  It links to the tenth, eleventh, and thirteenth screen, as well as a link back to the first screen.  It has no galleries or forms.  There is also a link back to the first screen.
• The thirteenth and final screen just has a control for entering in the name of a client that cannot be found in the tables from Data Sources #2 and #3.  Submitting will send an email to a support inbox making a request for a project number for the client entered into the control.  There are no galleries or forms, but there is a link back to the twelfth screen.