Start Updating a field

Updating a field

I have been exploring different methods of editing/updating a record within Entity Framework 5 in an ASP.

Despite that, you might find users prefer a quick macro.

The idea might seem like overkill — but if a simple macro eliminates user confusion and mistakes, a macro is worth the effort. The False value enters the date or time as a string.

I want to trigger a workflow only when a value is updated in a list item, but not everytime the item is changed.

For example I have a column for approve/not approve and I want that to be the trigger not the other values in the item.

Ali, Thanks, but this is something I already have set up.

The problem is that after the value is updated, everytime the item is changed (other columns that the one that trigger the workflow) the workflow restars, and in my case re-sends an email (it was set up to Actions: send an email). Thanks, You probably need two workflows, a hidden field and a "Start another workflow activity" (which can be found on Code Plex) Workflow 1 is a helper workflow which is set to start when an item is changed: It check if Status is equal to hidden field If it is the exit If not then start workflow 2 and set hidden field to current value of Status Workflow 2 is then the real workflow which does what you want when Status is changed @Marius: The first step in the workflow should be to compare the field value and provide a logic branch.

If you change that argument to True, Word will treat the inserted date or time as a field value.

Add a couple of custom buttons for both macros and take all the guesswork out of entering the current date and time.

Note: A custom installed form template is a form template that is installed on users' computers by means of a Microsoft Windows Installer (MSI) package or other Setup program.

With this type of form template, you must manually reinstall the form template on users' computers each time you update it.

And more secure (no need to fear about malicious "hidden fields" or things like that)I think you are right, my bad for trying to overlook View Models. I usually go one step further as per Dino Esposito's blog and create Input Models too, a tad belt and braces but it works quite well.