cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

The formula contains 'ParenClose' where 'Eof' is expected.

Not really sure why I am getting this error. I have tried removing parenthesis. Also, tried adding another parenthesis with semi colon. Nothing seems to work. Any ideas? Thank you.

eof1.png

 

With({data: NewIncidentForm.LastSubmit},

 // SEND NOTICE TO ALL SELECTED GROUPS
 ForAll(emaillist,
 Office365Outlook.SendEmailV2(
 EmailAddr,
 Coalesce(data.billto, data.name) & "- New Incident - " & data.incident_num,
 "<b>Incident Number: </b>" & data.incident_num & "<br>
 <b>Name: </b>" & data.name & "<br>
 <b>Incident Date: </b>" & data.inc_date & "<br>
 <b>Reported By: </b>" & data.reportedby & "<br>
 <b>Date Reported: </b>" & Today() & "<br>
 <b>Report Group: </b>" & Concat(RptGrpDropDown.SelectedItems, Text(RptGrp) & " ") & "<br>
 <b>Trip #: </b>" & data.trip & "<br>
 <b>Tractor: </b>" & data.tractor & "<br>
 <b>Trailer: </b>" & data.trailer & "<br>
 <b>Bill To: </b>" & data.billto & " - " & BillToName.Text & "<br>
 <b>Consignee: </b>" & data.consignee & " - " & ConsigneeName.Text & "<br>
 <b>Shipper: </b>" & data.shipper & " - " & ShipperName.Text & "<br>
 <b>Location of Incident: </b>" & data.location & "<br>
 <b>Description of Incident: </b>" & data.description & "<br>
 <b>At Fault: </b>" & data.fault & "<br>
 <b>Preventable: </b>" & data.prevent & "<br>
 <b>Status: </b>" & data.status
 );

 // SEND NOTICE TO INTERNAL STAFF
 Office365Outlook.SendEmailV2(
 "xxxx@xxxx.com; xxxx@xxxx.com",
 data.name & "- New Incident - " & data.incident_num,
 "<b>Incident Date: </b>" & data.inc_date & "<br>
 <b>Incident Number: </b>" & data.incident_num & "<br>
 <b>Name: </b>" & data.name & "<br>
 <b>Date Reported: </b>" & Today() & "<br>
 <b>Trip #: </b>" & data.trip & "<br>
 <b>Tractor: </b>" & data.tractor & "<br>
 <b>Trailer: </b>" & data.trailer & "<br>
 <b>Bill To: </b>" & data.billto & " - " & BillToName.Text & "<br>
 <b>Consignee: </b>" & data.consignee & " - " & ConsigneeName.Text & "<br>
 <b>Shipper: </b>" & data.shipper & " - " & ShipperName.Text & "<br>
 <b>Location of Incident: </b>" & data.location & "<br>
 <b>Description of Incident: </b>" & data.description & "<br>
 <b>At Fault: </b>" & data.fault & "<br>
 <b>Preventable: </b>" & data.prevent & "<br>
 <b>Status: </b>" & data.status &"<br>
 <b>Reported By: </b>" & data.reportedby & "<br>
 <b>Report Group: </b>" & Concat(RptGrpDropDown.SelectedItems, Text(RptGrp) & " ")
 );

Office365Outlook.SendEmailV2(
 User().Email,
 "Incident Submitted - " & data.incident_num,
 "<b>Your incident has been submitted successfully</b>"
);


Reset(cbCustomer);
 Reset(cbEmployID);
 Reset(cbOwnerOp);
 ResetForm(NewIncidentForm);
 Navigate(NewIncidentSuccess, ScreenTransition.Cover)

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Hello again @Anonymous 

Funny...I still had this formula up on my screen from a month ago when we went through it.

I believe the correction below is what you want (and why you are not seeing the email to the exec - because the closing parens for the ForAll were put in the wrong place.

This should be the correct version.

With({data: NewIncidentForm.LastSubmit},

   // SEND EMAIL TO SELECTED GROUPS
   ForAll(emaillist,
     Office365Outlook.SendEmailV2(EmailAddr,
        Coalesce(data.billto, data.name) & "- New Incident - " & data.incident_num,
        "<b>Incident Number: </b>" & data.incident_num & "<br>
         <b>Name: </b>" & data.name & "<br>
         <b>Incident Date: </b>" & data.inc_date & "<br>
         <b>Reported By: </b>" & data.reportedby & "<br>
         <b>Date Reported: </b>" & Today() & "<br>
         <b>Report Group: </b>" & Concat(RptGrpDropDown.SelectedItems, Text(RptGrp) & " ") & " 
         <br>
         <b>Trip #: </b>" & data.trip & "<br>
         <b>Tractor: </b>" & data.tractor & "<br>
         <b>Trailer: </b>" & data.trailer & "<br>
         <b>Bill To: </b>" & data.billto & " - " & BillToName.Text & "<br>
         <b>Consignee: </b>" & data.consignee & " - " & ConsigneeName.Text & "<br>
         <b>Shipper: </b>" & data.shipper & " - " & ShipperName.Text & "<br>
         <b>Location of Incident: </b>" & data.location & "<br>
         <b>Description of Incident: </b>" & data.description & "<br>
         <b>At Fault: </b>" & data.fault & "<br>
         <b>Preventable: </b>" & data.prevent & "<br>
         <b>Status: </b>" & data.status
    )
  );

   // SEND EMAL TO EXECUTIVES
   Office365Outlook.SendEmailV2(
      "xx@xx.com; xx@xx.com",data.name & "- New Incident - " & data.incident_num,
      "<b>Incident Date: </b>" & data.inc_date & "<br>
       <b>Incident Number: </b>" & data.incident_num & "<br>
       <b>Name: </b>" & data.name & "<br>
       <b>Date Reported: </b>" & Today() & "<br>
       <b>Trip #: </b>" & data.trip & "<br>
       <b>Tractor: </b>" & data.tractor & "<br>
       <b>Trailer: </b>" & data.trailer & "<br>
       <b>Bill To: </b>" & data.billto & " - " & BillToName.Text & "<br>
       <b>Consignee: </b>" & data.consignee & " - " & ConsigneeName.Text & "<br>
       <b>Shipper: </b>" & data.shipper & " - " & ShipperName.Text & "<br>
       <b>Location of Incident: </b>" & data.location & "<br>
       <b>Description of Incident: </b>" & data.description & "<br>
       <b>At Fault: </b>" & data.fault & "<br>
       <b>Preventable: </b>" & data.prevent & "<br>
       <b>Status: </b>" & data.status &"<br>
       <b>Reported By: </b>" & data.reportedby & "<br>
       <b>Report Group: </b>" & Concat(RptGrpDropDown.SelectedItems, Text(RptGrp) & " ")
    );

    Office365Outlook.SendEmailV2(
      User().Email,
      "Incident Submitted - " & data.incident_num,
      "<b>Your incident has been submitted successfully</b>"
    )
);

 Reset(cbCustomer);
 Reset(cbEmployID);
 Reset(cbOwnerOp);
 ResetForm(NewIncidentForm);
 Navigate(NewIncidentSuccess, ScreenTransition.Cover)

 

This will at least send to the execs and the user.  The emaillist is the next thing to look at.

What I don't seem to have any more is where we were getting emaillist from?  I thought that was a dropdown or combobox or something.

Please clarify again.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

View solution in original post

48 REPLIES 48
mdevaney
Super User
Super User

@Anonymous 

I think you just forgot to close your WITH statement, that's all.  Here's my idea:

With({data: NewIncidentForm.LastSubmit},

 // SEND NOTICE TO ALL SELECTED GROUPS
 ForAll(emaillist,
 Office365Outlook.SendEmailV2(
 EmailAddr,
 Coalesce(data.billto, data.name) & "- New Incident - " & data.incident_num,
 "<b>Incident Number: </b>" & data.incident_num & "<br>
 <b>Name: </b>" & data.name & "<br>
 <b>Incident Date: </b>" & data.inc_date & "<br>
 <b>Reported By: </b>" & data.reportedby & "<br>
 <b>Date Reported: </b>" & Today() & "<br>
 <b>Report Group: </b>" & Concat(RptGrpDropDown.SelectedItems, Text(RptGrp) & " ") & "<br>
 <b>Trip #: </b>" & data.trip & "<br>
 <b>Tractor: </b>" & data.tractor & "<br>
 <b>Trailer: </b>" & data.trailer & "<br>
 <b>Bill To: </b>" & data.billto & " - " & BillToName.Text & "<br>
 <b>Consignee: </b>" & data.consignee & " - " & ConsigneeName.Text & "<br>
 <b>Shipper: </b>" & data.shipper & " - " & ShipperName.Text & "<br>
 <b>Location of Incident: </b>" & data.location & "<br>
 <b>Description of Incident: </b>" & data.description & "<br>
 <b>At Fault: </b>" & data.fault & "<br>
 <b>Preventable: </b>" & data.prevent & "<br>
 <b>Status: </b>" & data.status
 );

 // SEND NOTICE TO INTERNAL STAFF
 Office365Outlook.SendEmailV2(
 "xxxx@xxxx.com; xxxx@xxxx.com",
 data.name & "- New Incident - " & data.incident_num,
 "<b>Incident Date: </b>" & data.inc_date & "<br>
 <b>Incident Number: </b>" & data.incident_num & "<br>
 <b>Name: </b>" & data.name & "<br>
 <b>Date Reported: </b>" & Today() & "<br>
 <b>Trip #: </b>" & data.trip & "<br>
 <b>Tractor: </b>" & data.tractor & "<br>
 <b>Trailer: </b>" & data.trailer & "<br>
 <b>Bill To: </b>" & data.billto & " - " & BillToName.Text & "<br>
 <b>Consignee: </b>" & data.consignee & " - " & ConsigneeName.Text & "<br>
 <b>Shipper: </b>" & data.shipper & " - " & ShipperName.Text & "<br>
 <b>Location of Incident: </b>" & data.location & "<br>
 <b>Description of Incident: </b>" & data.description & "<br>
 <b>At Fault: </b>" & data.fault & "<br>
 <b>Preventable: </b>" & data.prevent & "<br>
 <b>Status: </b>" & data.status &"<br>
 <b>Reported By: </b>" & data.reportedby & "<br>
 <b>Report Group: </b>" & Concat(RptGrpDropDown.SelectedItems, Text(RptGrp) & " ")
 );

Office365Outlook.SendEmailV2(
 User().Email,
 "Incident Submitted - " & data.incident_num,
 "<b>Your incident has been submitted successfully</b>"
);

) // I added this bracket

Reset(cbCustomer);
 Reset(cbEmployID);
 Reset(cbOwnerOp);
 ResetForm(NewIncidentForm);
 Navigate(NewIncidentSuccess, ScreenTransition.Cover)

 

---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."

Anonymous
Not applicable

@mdevaney 

 

Thanks for the quick reply! When I added your bracket, I still have the same error plus a new error. See below. Thank you.

123.png1234.png

@Anonymous 

Good lord, haha.  I forgot the semi-colon.

 

ith({data: NewIncidentForm.LastSubmit},

 // SEND NOTICE TO ALL SELECTED GROUPS
 ForAll(emaillist,
 Office365Outlook.SendEmailV2(
 EmailAddr,
 Coalesce(data.billto, data.name) & "- New Incident - " & data.incident_num,
 "<b>Incident Number: </b>" & data.incident_num & "<br>
 <b>Name: </b>" & data.name & "<br>
 <b>Incident Date: </b>" & data.inc_date & "<br>
 <b>Reported By: </b>" & data.reportedby & "<br>
 <b>Date Reported: </b>" & Today() & "<br>
 <b>Report Group: </b>" & Concat(RptGrpDropDown.SelectedItems, Text(RptGrp) & " ") & "<br>
 <b>Trip #: </b>" & data.trip & "<br>
 <b>Tractor: </b>" & data.tractor & "<br>
 <b>Trailer: </b>" & data.trailer & "<br>
 <b>Bill To: </b>" & data.billto & " - " & BillToName.Text & "<br>
 <b>Consignee: </b>" & data.consignee & " - " & ConsigneeName.Text & "<br>
 <b>Shipper: </b>" & data.shipper & " - " & ShipperName.Text & "<br>
 <b>Location of Incident: </b>" & data.location & "<br>
 <b>Description of Incident: </b>" & data.description & "<br>
 <b>At Fault: </b>" & data.fault & "<br>
 <b>Preventable: </b>" & data.prevent & "<br>
 <b>Status: </b>" & data.status
 );

 // SEND NOTICE TO INTERNAL STAFF
 Office365Outlook.SendEmailV2(
 "xxxx@xxxx.com; xxxx@xxxx.com",
 data.name & "- New Incident - " & data.incident_num,
 "<b>Incident Date: </b>" & data.inc_date & "<br>
 <b>Incident Number: </b>" & data.incident_num & "<br>
 <b>Name: </b>" & data.name & "<br>
 <b>Date Reported: </b>" & Today() & "<br>
 <b>Trip #: </b>" & data.trip & "<br>
 <b>Tractor: </b>" & data.tractor & "<br>
 <b>Trailer: </b>" & data.trailer & "<br>
 <b>Bill To: </b>" & data.billto & " - " & BillToName.Text & "<br>
 <b>Consignee: </b>" & data.consignee & " - " & ConsigneeName.Text & "<br>
 <b>Shipper: </b>" & data.shipper & " - " & ShipperName.Text & "<br>
 <b>Location of Incident: </b>" & data.location & "<br>
 <b>Description of Incident: </b>" & data.description & "<br>
 <b>At Fault: </b>" & data.fault & "<br>
 <b>Preventable: </b>" & data.prevent & "<br>
 <b>Status: </b>" & data.status &"<br>
 <b>Reported By: </b>" & data.reportedby & "<br>
 <b>Report Group: </b>" & Concat(RptGrpDropDown.SelectedItems, Text(RptGrp) & " ")
 );

Office365Outlook.SendEmailV2(
 User().Email,
 "Incident Submitted - " & data.incident_num,
 "<b>Your incident has been submitted successfully</b>"
)

); // I added this bracket and a colon

Reset(cbCustomer);
Reset(cbEmployID);
Reset(cbOwnerOp);
ResetForm(NewIncidentForm);
Navigate(NewIncidentSuccess, ScreenTransition.Cover);

 

---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."

Anonymous
Not applicable

@mdevaney 

 

Ha! That cleared up the first error, but I still have the original error. This is confusing me, as these formulas are usually pretty easy and work well, not sure what I did wrong.

12.png

@Anonymous 
Maybe two brackets are needed because there is also a FORALL loop I missed earlier

 

With({data: NewIncidentForm.LastSubmit},

 // SEND NOTICE TO ALL SELECTED GROUPS
 ForAll(emaillist,
 Office365Outlook.SendEmailV2(
 EmailAddr,
 Coalesce(data.billto, data.name) & "- New Incident - " & data.incident_num,
 "<b>Incident Number: </b>" & data.incident_num & "<br>
 <b>Name: </b>" & data.name & "<br>
 <b>Incident Date: </b>" & data.inc_date & "<br>
 <b>Reported By: </b>" & data.reportedby & "<br>
 <b>Date Reported: </b>" & Today() & "<br>
 <b>Report Group: </b>" & Concat(RptGrpDropDown.SelectedItems, Text(RptGrp) & " ") & "<br>
 <b>Trip #: </b>" & data.trip & "<br>
 <b>Tractor: </b>" & data.tractor & "<br>
 <b>Trailer: </b>" & data.trailer & "<br>
 <b>Bill To: </b>" & data.billto & " - " & BillToName.Text & "<br>
 <b>Consignee: </b>" & data.consignee & " - " & ConsigneeName.Text & "<br>
 <b>Shipper: </b>" & data.shipper & " - " & ShipperName.Text & "<br>
 <b>Location of Incident: </b>" & data.location & "<br>
 <b>Description of Incident: </b>" & data.description & "<br>
 <b>At Fault: </b>" & data.fault & "<br>
 <b>Preventable: </b>" & data.prevent & "<br>
 <b>Status: </b>" & data.status
 );

 // SEND NOTICE TO INTERNAL STAFF
 Office365Outlook.SendEmailV2(
 "xxxx@xxxx.com; xxxx@xxxx.com",
 data.name & "- New Incident - " & data.incident_num,
 "<b>Incident Date: </b>" & data.inc_date & "<br>
 <b>Incident Number: </b>" & data.incident_num & "<br>
 <b>Name: </b>" & data.name & "<br>
 <b>Date Reported: </b>" & Today() & "<br>
 <b>Trip #: </b>" & data.trip & "<br>
 <b>Tractor: </b>" & data.tractor & "<br>
 <b>Trailer: </b>" & data.trailer & "<br>
 <b>Bill To: </b>" & data.billto & " - " & BillToName.Text & "<br>
 <b>Consignee: </b>" & data.consignee & " - " & ConsigneeName.Text & "<br>
 <b>Shipper: </b>" & data.shipper & " - " & ShipperName.Text & "<br>
 <b>Location of Incident: </b>" & data.location & "<br>
 <b>Description of Incident: </b>" & data.description & "<br>
 <b>At Fault: </b>" & data.fault & "<br>
 <b>Preventable: </b>" & data.prevent & "<br>
 <b>Status: </b>" & data.status &"<br>
 <b>Reported By: </b>" & data.reportedby & "<br>
 <b>Report Group: </b>" & Concat(RptGrpDropDown.SelectedItems, Text(RptGrp) & " ")
 );

Office365Outlook.SendEmailV2(
 User().Email,
 "Incident Submitted - " & data.incident_num,
 "<b>Your incident has been submitted successfully</b>"
)

)); // I added two brackets and a colon

Reset(cbCustomer);
Reset(cbEmployID);
Reset(cbOwnerOp);
ResetForm(NewIncidentForm);
Navigate(NewIncidentSuccess, ScreenTransition.Cover);

 

---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."

carfup
Resolver I
Resolver I

Hi,
You're missing two ")" to close the ForAll and With functions.
Clément

@carfup 

Yep, agreed.  I finally came to that conclusion above after I placed it in the code editor. Thanks for confirming 🙂

Anonymous
Not applicable

@mdevaney 

@carfup 

 

That extra bracket took care of all the errors. However, it is not emailing now. It seems that it is not collecting the email address for the emaillist, which I use in the formula to email multiple emails. Although not entirely sure because it doesn't email to the executives either which is the 2nd email formula.

 

With({data: NewIncidentForm.LastSubmit},

 // SEND EMAIL TO SELECTED GROUPS
 ForAll(emaillist,Office365Outlook.SendEmailV2(EmailAddr,
 Coalesce(data.billto, data.name) & "- New Incident - " & data.incident_num,
 "<b>Incident Number: </b>" & data.incident_num & "<br>
 <b>Name: </b>" & data.name & "<br>
 <b>Incident Date: </b>" & data.inc_date & "<br>
 <b>Reported By: </b>" & data.reportedby & "<br>
 <b>Date Reported: </b>" & Today() & "<br>
 <b>Report Group: </b>" & Concat(RptGrpDropDown.SelectedItems, Text(RptGrp) & " ") & "<br>
 <b>Trip #: </b>" & data.trip & "<br>
 <b>Tractor: </b>" & data.tractor & "<br>
 <b>Trailer: </b>" & data.trailer & "<br>
 <b>Bill To: </b>" & data.billto & " - " & BillToName.Text & "<br>
 <b>Consignee: </b>" & data.consignee & " - " & ConsigneeName.Text & "<br>
 <b>Shipper: </b>" & data.shipper & " - " & ShipperName.Text & "<br>
 <b>Location of Incident: </b>" & data.location & "<br>
 <b>Description of Incident: </b>" & data.description & "<br>
 <b>At Fault: </b>" & data.fault & "<br>
 <b>Preventable: </b>" & data.prevent & "<br>
 <b>Status: </b>" & data.status
 );

 // SEND EMAL TO EXECUTIVES
 Office365Outlook.SendEmailV2("xx@xx.com; xx@xx.com",data.name & "- New Incident - " & data.incident_num,
 "<b>Incident Date: </b>" & data.inc_date & "<br>
 <b>Incident Number: </b>" & data.incident_num & "<br>
 <b>Name: </b>" & data.name & "<br>
 <b>Date Reported: </b>" & Today() & "<br>
 <b>Trip #: </b>" & data.trip & "<br>
 <b>Tractor: </b>" & data.tractor & "<br>
 <b>Trailer: </b>" & data.trailer & "<br>
 <b>Bill To: </b>" & data.billto & " - " & BillToName.Text & "<br>
 <b>Consignee: </b>" & data.consignee & " - " & ConsigneeName.Text & "<br>
 <b>Shipper: </b>" & data.shipper & " - " & ShipperName.Text & "<br>
 <b>Location of Incident: </b>" & data.location & "<br>
 <b>Description of Incident: </b>" & data.description & "<br>
 <b>At Fault: </b>" & data.fault & "<br>
 <b>Preventable: </b>" & data.prevent & "<br>
 <b>Status: </b>" & data.status &"<br>
 <b>Reported By: </b>" & data.reportedby & "<br>
 <b>Report Group: </b>" & Concat(RptGrpDropDown.SelectedItems, Text(RptGrp) & " ")
 );

Office365Outlook.SendEmailV2(
 User().Email,
 "Incident Submitted - " & data.incident_num,
 "<b>Your incident has been submitted successfully</b>"
);

)); // I added this bracket

 Reset(cbCustomer);
 Reset(cbEmployID);
 Reset(cbOwnerOp);
 ResetForm(NewIncidentForm);
 Navigate(NewIncidentSuccess, ScreenTransition.Cover)

 

 

Correct me if i'm wrong, but i feel like your ForAll loop is only the emailing to groups ? 
If so the closing of that function is not at the correct place and should look like : 

 

With({data: NewIncidentForm.LastSubmit},

 // SEND EMAIL TO SELECTED GROUPS
 ForAll(emaillist,Office365Outlook.SendEmailV2(EmailAddr,
 Coalesce(data.billto, data.name) & "- New Incident - " & data.incident_num,
 "<b>Incident Number: </b>" & data.incident_num & "<br>
 <b>Name: </b>" & data.name & "<br>
 <b>Incident Date: </b>" & data.inc_date & "<br>
 <b>Reported By: </b>" & data.reportedby & "<br>
 <b>Date Reported: </b>" & Today() & "<br>
 <b>Report Group: </b>" & Concat(RptGrpDropDown.SelectedItems, Text(RptGrp) & " ") & "<br>
 <b>Trip #: </b>" & data.trip & "<br>
 <b>Tractor: </b>" & data.tractor & "<br>
 <b>Trailer: </b>" & data.trailer & "<br>
 <b>Bill To: </b>" & data.billto & " - " & BillToName.Text & "<br>
 <b>Consignee: </b>" & data.consignee & " - " & ConsigneeName.Text & "<br>
 <b>Shipper: </b>" & data.shipper & " - " & ShipperName.Text & "<br>
 <b>Location of Incident: </b>" & data.location & "<br>
 <b>Description of Incident: </b>" & data.description & "<br>
 <b>At Fault: </b>" & data.fault & "<br>
 <b>Preventable: </b>" & data.prevent & "<br>
 <b>Status: </b>" & data.status
 );
 );

 // SEND EMAL TO EXECUTIVES
 Office365Outlook.SendEmailV2("xx@xx.com; xx@xx.com",data.name & "- New Incident - " & data.incident_num,
 "<b>Incident Date: </b>" & data.inc_date & "<br>
 <b>Incident Number: </b>" & data.incident_num & "<br>
 <b>Name: </b>" & data.name & "<br>
 <b>Date Reported: </b>" & Today() & "<br>
 <b>Trip #: </b>" & data.trip & "<br>
 <b>Tractor: </b>" & data.tractor & "<br>
 <b>Trailer: </b>" & data.trailer & "<br>
 <b>Bill To: </b>" & data.billto & " - " & BillToName.Text & "<br>
 <b>Consignee: </b>" & data.consignee & " - " & ConsigneeName.Text & "<br>
 <b>Shipper: </b>" & data.shipper & " - " & ShipperName.Text & "<br>
 <b>Location of Incident: </b>" & data.location & "<br>
 <b>Description of Incident: </b>" & data.description & "<br>
 <b>At Fault: </b>" & data.fault & "<br>
 <b>Preventable: </b>" & data.prevent & "<br>
 <b>Status: </b>" & data.status &"<br>
 <b>Reported By: </b>" & data.reportedby & "<br>
 <b>Report Group: </b>" & Concat(RptGrpDropDown.SelectedItems, Text(RptGrp) & " ")
 );

Office365Outlook.SendEmailV2(
 User().Email,
 "Incident Submitted - " & data.incident_num,
 "<b>Your incident has been submitted successfully</b>"
);

); // I added this bracket

 Reset(cbCustomer);
 Reset(cbEmployID);
 Reset(cbOwnerOp);
 ResetForm(NewIncidentForm);
 Navigate(NewIncidentSuccess, ScreenTransition.Cover)

 

Helpful resources

Announcements

Exclusive LIVE Community Event: Power Apps Copilot Coffee Chat with Copilot Studio Product Team

  It's time for the SECOND Power Apps Copilot Coffee Chat featuring the Copilot Studio product team, which will be held LIVE on April 3, 2024 at 9:30 AM Pacific Daylight Time (PDT).     This is an incredible opportunity to connect with members of the Copilot Studio product team and ask them anything about Copilot Studio. We'll share our special guests with you shortly--but we want to encourage to mark your calendars now because you will not want to miss the conversation.   This live event will give you the unique opportunity to learn more about Copilot Studio plans, where we’ll focus, and get insight into upcoming features. We’re looking forward to hearing from the community, so bring your questions!   TO GET ACCESS TO THIS EXCLUSIVE AMA: Kudo this post to reserve your spot! Reserve your spot now by kudoing this post.  Reservations will be prioritized on when your kudo for the post comes through, so don't wait! Click that "kudo button" today.   Invitations will be sent on April 2nd.Users posting Kudos after April 2nd. at 9AM PDT may not receive an invitation but will be able to view the session online after conclusion of the event. Give your "kudo" today and mark your calendars for April 3rd, 2024 at 9:30 AM PDT and join us for an engaging and informative session!

Tuesday Tip: Unlocking Community Achievements and Earning Badges

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!     THIS WEEK'S TIP: Unlocking Achievements and Earning BadgesAcross the Communities, you'll see badges on users profile that recognize and reward their engagement and contributions. These badges each signify a different achievement--and all of those achievements are available to any Community member! If you're a seasoned pro or just getting started, you too can earn badges for the great work you do. Check out some details on Community badges below--and find out more in the detailed link at the end of the article!       A Diverse Range of Badges to Collect The badges you can earn in the Community cover a wide array of activities, including: Kudos Received: Acknowledges the number of times a user’s post has been appreciated with a “Kudo.”Kudos Given: Highlights the user’s generosity in recognizing others’ contributions.Topics Created: Tracks the number of discussions initiated by a user.Solutions Provided: Celebrates the instances where a user’s response is marked as the correct solution.Reply: Counts the number of times a user has engaged with community discussions.Blog Contributor: Honors those who contribute valuable content and are invited to write for the community blog.       A Community Evolving Together Badges are not only a great way to recognize outstanding contributions of our amazing Community members--they are also a way to continue fostering a collaborative and supportive environment. As you continue to share your knowledge and assist each other these badges serve as a visual representation of your valuable contributions.   Find out more about badges in these Community Support pages in each Community: All About Community Badges - Power Apps CommunityAll About Community Badges - Power Automate CommunityAll About Community Badges - Copilot Studio CommunityAll About Community Badges - Power Pages Community

Tuesday Tips: Powering Up Your Community Profile

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!   This Week's Tip: Power Up Your Profile!  🚀 It's where every Community member gets their start, and it's essential that you keep it updated! Your Community User Profile is how you're able to get messages, post solutions, ask questions--and as you rank up, it's where your badges will appear and how you'll be known when you start blogging in the Community Blog. Your Community User Profile is how the Community knows you--so it's essential that it works the way you need it to! From changing your username to updating contact information, this Knowledge Base Article is your best resource for powering up your profile.     Password Puzzles? No Problem! Find out how to sync your Azure AD password with your community account, ensuring a seamless sign-in. No separate passwords to remember! Job Jumps & Email Swaps Changed jobs? Got a new email? Fear not! You'll find out how to link your shiny new email to your existing community account, keeping your contributions and connections intact. Username Uncertainties Unraveled Picking the perfect username is crucial--and sometimes the original choice you signed up with doesn't fit as well as you may have thought. There's a quick way to request an update here--but remember, your username is your community identity, so choose wisely. "Need Admin Approval" Warning Window? If you see this error message while using the community, don't worry. A simple process will help you get where you need to go. If you still need assistance, find out how to contact your Community Support team. Whatever you're looking for, when it comes to your profile, the Community Account Support Knowledge Base article is your treasure trove of tips as you navigate the nuances of your Community Profile. It’s the ultimate resource for keeping your digital identity in tip-top shape while engaging with the Power Platform Community. So, dive in and power up your profile today!  💪🚀   Community Account Support | Power Apps Community Account Support | Power AutomateCommunity Account Support | Copilot Studio  Community Account Support | Power Pages

Super User of the Month | Chris Piasecki

In our 2nd installment of this new ongoing feature in the Community, we're thrilled to announce that Chris Piasecki is our Super User of the Month for March 2024. If you've been in the Community for a while, we're sure you've seen a comment or marked one of Chris' helpful tips as a solution--he's been a Super User for SEVEN consecutive seasons!       Since authoring his first reply in April 2020 to his most recent achievement organizing the Canadian Power Platform Summit this month, Chris has helped countless Community members with his insights and expertise. In addition to being a Super User, Chris is also a User Group leader, Microsoft MVP, and a featured speaker at the Microsoft Power Platform Conference. His contributions to the new SUIT program, along with his joyous personality and willingness to jump in and help so many members has made Chris a fixture in the Power Platform Community.   When Chris isn't authoring solutions or organizing events, he's actively leading Piasecki Consulting, specializing in solution architecture, integration, DevOps, and more--helping clients discover how to strategize and implement Microsoft's technology platforms. We are grateful for Chris' insightful help in the Community and look forward to even more amazing milestones as he continues to assist so many with his great tips, solutions--always with a smile and a great sense of humor.You can find Chris in the Community and on LinkedIn. Thanks for being such a SUPER user, Chris! 💪🌠

Tuesday Tips: Community Ranks and YOU

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!This Week: Community Ranks--Moving from "Member" to "Community Champion"   Have you ever wondered how your fellow community members ascend the ranks within our community? What sets apart an Advocate from a Helper, or a Solution Sage from a Community Champion? In today’s #TuesdayTip, we’re unveiling the secrets and sharing tips to help YOU elevate your ranking—and why it matters to our vibrant communities. Community ranks serve as a window into a member’s role and activity. They celebrate your accomplishments and reveal whether someone has been actively contributing and assisting others. For instance, a Super User is someone who has been exceptionally helpful and engaged. Some ranks even come with special permissions, especially those related to community management. As you actively participate—whether by creating new topics, providing solutions, or earning kudos—your rank can climb. Each time you achieve a new rank, you’ll receive an email notification. Look out for the icon and rank name displayed next to your username—it’s a badge of honor! Fun fact: Your Community Engagement Team keeps an eye on these ranks, recognizing the most passionate and active community members. So shine brightly with valuable content, and you might just earn well-deserved recognition! Where can you see someone’s rank? When viewing a post, you’ll find a member’s rank to the left of their name.Click on a username to explore their profile, where their rank is prominently displayed. What about the ranks themselves? New members start as New Members, progressing to Regular Visitors, and then Frequent Visitors.Beyond that, we have a categorized system: Kudo Ranks: Earned through kudos (teal icons).Post Ranks: Based on your posts (purple icons).Solution Ranks: Reflecting your solutions (green icons).Combo Ranks: These orange icons combine kudos, solutions, and posts. The top ranks have unique names, making your journey even more exciting! So dive in, collect those kudos, share solutions, and let’s see how high you can rank! 🌟 🚀   Check out the Using the Community boards in each of the communities for more helpful information!  Power Apps, Power Automate, Copilot Studio & Power Pages

Find Out What Makes Super Users So Super

We know many of you visit the Power Platform Communities to ask questions and receive answers. But do you know that many of our best answers and solutions come from Community members who are super active, helping anyone who needs a little help getting unstuck with Business Applications products? We call these dedicated Community members Super Users because they are the real heroes in the Community, willing to jump in whenever they can to help! Maybe you've encountered them yourself and they've solved some of your biggest questions. Have you ever wondered, "Why?"We interviewed several of our Super Users to understand what drives them to help in the Community--and discover the difference it has made in their lives as well! Take a look in our gallery today: What Motivates a Super User? - Power Platform Community (microsoft.com)

Top Solution Authors
Top Kudoed Authors
Users online (7,001)