web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Power Apps - Building Power Apps
Unanswered

Possible bug: Receive error message "Title: Field 'Title' is required" even when that is false

(0) ShareShare
ReportReport
Posted on by

Hello!

I think I may have encountered a bug, or I'm simply missing something. I have made an app very similar to the one described in this thread. It works as intended, except I sometimes receive the error message "Title: Field 'Title' is required" when I press the Submit button. Even when the error appears, the records are created successfully.

I originally renamed the Title column to EquipmentID. I have tried to eliminate the error message in these ways:

  • Change EquipmentID to Title in the OnSelect code
  • Rename the EquipmentID column back to Title in the SharePoint list
  • Make the EquipmentID column not required in the SharePoint list

Again, the app always works fine, but I would like to get rid of this weird error so users don't think that something went wrong. If anyone has any ideas on how to fix this, I would greatly appreciate it. I have added my Submit button's OnSelect code below, but if any other details would be helpful don't hesitate to ask.

Thanks in advance,

Matt

(Also, I'm very new to Power Apps, so if you notice any other ways I could improve my code, I'd love to hear them!)

 

Submit button OnSelect code:

ClearCollect(
 colCounter,
 FirstN(
 NumberCollection,
 Value(QuantityInput.Text)
 )
);
Set(
 IDPrefix,
 Left(
 EquipmentTypeDropDown.Selected.Value,
 1
 ) & Text(
 PurchaseDatePicker.SelectedDate,
 "[$-en-US]yymm"
 )
);
Set(
 LookupRecord,
 LookUp(
 'Matt Test 2',
 ThisRecord.Prefix = IDPrefix
 )
);
Set(
 PrevIndex,
 If(
 IsBlank(LookupRecord),
 0,
 LookupRecord.LastIndex
 )
);
Clear(colNewRecords);
ForAll(
 colCounter,
 Collect(
 colNewRecords,
 Defaults(EquipmentIDs),
 {
 Title: IDPrefix & Text(
 Value(PrevIndex + ThisRecord.Value),
 "[$-en-US]0000"
 ),
 PurchaseDate: PurchaseDatePicker.SelectedDate,
 EquipmentType: EquipmentTypeDropDown.SelectedText,
 Manufacturer: ManufacturerDropDown.SelectedText,
 Model: ModelInput.Text,
 Comments: NotesInput.Text
 }
 )
);
Patch(
 EquipmentIDs,
 colNewRecords
);
Patch(
 'Matt Test 2',
 If(
 IsBlank(LookupRecord),
 Defaults('Matt Test 2'),
 LookupRecord
 ),
 If(
 IsBlank(LookupRecord),
 {
 Prefix: IDPrefix,
 LastIndex: PrevIndex + Value(QuantityInput.Text)
 },
 {LastIndex: PrevIndex + Value(QuantityInput.Text)}
 )
);
Navigate(
 ResultScreen,
 ScreenTransition.Cover
)
I have the same question (0)
  • Community Power Platform Member Profile Picture
    on at
    Re: Possible bug: Receive error message "Title: Field 'Title' is required" even when that is false

    @Tryin2MakeApps 

    Those 3 checks you've tried should've fixed the error. Things you could try are

     

    1. Refresh your data source then remove the Title/EquipmentID datacard from your form. Then add it back in.

    2. Wait. Sometimes these changes can take a little time to come through at the SharePoint side and waiting is all you can do.

  • amit1030 Profile Picture
    34 on at
    Re: Possible bug: Receive error message "Title: Field 'Title' is required" even when that is false

    Hi @Tryin2MakeApps  ,

     

    I think you should go to the SharePoint list setting and you will find the column name. Just select the column name "Title" and uncheck the "Required" option. Once you make all these changes then refresh your database in the power app then go to the "onstart" property and click on start or simply close your powerapp and reopen your powerapp. Maybe your problem will be resolved at least for "Title: field is missing".

     

    If still, you are facing the problem then you need to make changes in your code.  

     

  • RandyHayes Profile Picture
    76,291 Super User 2024 Season 1 on at
    Re: Possible bug: Receive error message "Title: Field 'Title' is required" even when that is false

    @Tryin2MakeApps 

    Keep this in mind, when you create a column in SharePoint it is given a name.  You can never change that real name.  You can change what appears to be the name of it and SharePoint will display it with your new name, but under the hood, it is still the original name.  Since a new list always has a Title column, even if you rename it, it is still Title.  PowerApps honors the new name you called it in some place and in other not so much.  So, if it was original called title, then go for that name first and if you don't see or get errors with the original name then look for the name you called it (as I mentioned, some places it is completely honored, others not).

     

    As for your Formula, as you asked for comments on your formula...I would consider not wasting the output of your ForAll.  ForAll is not a For/Loop as much as it is a function that creates records "for all" of your statements into a table.  So, use the output!  

    Use the With statement to create scope variables rather than global variables that will inevitably "junk up" and create a long list of variables to try and figure out what they are for.

    In your first block of Formula, you are getting a single value and putting it into a collection in order to ForAll it...if you have a single value, there is nothing to for/all over.  There is just one record.

    I am not sure of your datasources, but they appear to be potentially 'Matt Test 2' and EquipmentIDs.

    It appears that you are trying to set the Datasource EquipmentIDs (ultimately, not in this formula) to be either an update to an existing record or a new one.  I am not sure on that because you are using a Defaults(EquipmentIDs) in your formula to put into a collection.

    So, based on all of that above (and a few other assumptions made based on what I was seeing), your formula should be:

    With({IDPrefix: Left(EquipmentTypeDropDown.Selected.Value, 1) & Text(PurchaseDatePicker.SelectedDate, "[$-en-US]yymm"),
     LookUpRecord: LookUp('Matt Test 2', Prefix = IDPrefix)
     },
     
     Patch(EquipmentIDs,
     Coalesce(LookUpRecord, Defaults(EquipmentIDs)),
     {
     Title: IDPrefix & Text(Coalesce(LookUpRecord.LastIndex, 0) + Value, "[$-en-US]0000"),
     PurchaseDate: PurchaseDatePicker.SelectedDate,
     EquipmentType: EquipmentTypeDropDown.SelectedText, //THIS SHOULD BE REPLACED WITH .SELECTED.someColumn SELECTEDTEXT IS A DEPRECATED PROPERTY
     Manufacturer: ManufacturerDropDown.SelectedText, // SAME AS ABOVE
     Model: ModelInput.Text,
     Comments: NotesInput.Text
     }
     );
    
     Patch('Matt Test 2', Coalesce(LookUpRecord, Defaults('Matt Test 2')),
     {
     Prefix: IDPrefix,
     LastIndex: LookUpRecord.LastIndex + Value(QuantityInput.Text)
     }
     )
    );
    Navigate(ResultScreen, ScreenTransition.Cover)

    I am not clear on what you were originally doing with the Patch(EquipmentIDs, colRecords).

     

    So, that is some feedback as you asked.  In general, avoid collections, get rid of variables and keep it simple.

     

    I hope this is helpful for you.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Chiara Carbone – Community Spotlight

We are honored to recognize Chiara Carbone as our Community Spotlight for November…

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 652 Most Valuable Professional

#2
Michael E. Gernaey Profile Picture

Michael E. Gernaey 410 Super User 2025 Season 2

#3
developerAJ Profile Picture

developerAJ 236

Last 30 days Overall leaderboard