nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Auto populate Date only once on forms that are edited multiple times

LindsayLewin

Hello.

I have a form that is edited by multiple users at various dates. There are 3 groups and each group has a date field that needs to be populated.

I'd like the dates to be autopopulated, and I've used date() function for all three fields, however, if the form is opened again at another date, all the date fields from previous entries are changed the current date.

I need to retain the original dates - is there are way to do this?

Many thanks,

Lindsay

Finde mehr Beiträge mit dem Tag

Accepted answers

All comments

Krocha

I was thinking i would have a separate field for who created the feature point (this is in case i have to re-publish the feature layer). It will grab the username by calculation in the forms but i wanted it to display as the full name of the user instead of the username. I believe i have tried but this does not work for offline maps.

KerriRasmussen

@Krocha the creator field is a system generated field and it will only populate when the feature is first created, meaning it won't update. The editor field will update when the feature is updated with the name of the latest editor (this is assuming that editor tracking is turned on for that feature). Is that what you were looking to do or did you have another workflow in mind?

Krocha

Is there a way to do this but with the creator field? I use offline maps in field maps.

LindsayLewin

SO i figured this out - on features that are already exisiting, where the user is no actually creating new geometry - UPDATE is used instead of INSERT.

Thanks for getting me started on that one 🙂

if ($editcontext.editType == "UPDATE") {

var originalDate = Today();

//keep original date

return originalDate;

} else {

return $originalFeature.SeedDate;

Lindsay.

LindsayLewin

Hey Kerry - after adding some new data - with no dates recorded as of yet - i see that there is an issue with the code capturing that first date submission.

If the field is null to begin with I need the user to submit that, then after retain that specific value throughout the lifecycle of the inspection.

I've tried to add a date() at the beginning of this expression with no luck - thoughts?

date()

if ($editcontext.editType == "INSERT") {

var originalDate = Today();

//keep original date

return originalDate;

} else {

return $originalFeature.SeedDate;

}

LindsayLewin

Worked like a charm! Many thanks!

KerriRasmussen

Hi Lindsay,

Good afternoon. You can use an Arcade expression on that field. I've included a sample below. You will need to update the name of your date field. This will capture the date when a new feature is added, but it will remain read only after that.

if ($editcontext.editType == "INSERT") {
   var originalDate = Today();

   //keep original date
   return originalDate;
} else {
  return $originalFeature.yourdatefield;
}

Nimm an der Unterhaltung teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.