I never thought that this tool would have such a history , but it is still saves me time every day. I am really exited about this release because a history of the values is being kept. This history will now be selectable in the prompt when entering a new value. The error handling and messages have also greatly improved. Download Edit Document 6.0.0 or if you would like to step threw the code break down and learn what is happening.
Changes
- Added the following new data type/actions:
- Added history to prompts. All prompts that where edits are now edit combo a history of ten values will be kept. Use 'cFieldHistoryValues' to set the amount of history to keep.
- Added prompt before updating documents to confirm what is going to happen. Set 'cEnableConfirmation' constant to @False to disable this feature. This information will always be printed to the status bar.
- All constants start with c, some can be customized as noted.
- Improved error message when validating the entered formula.
- Improved error message when executing the operation on a document.
- Added ability to continue executing the operation on all remaining documents even if an error occurs. Each time an error occurs there is an option to stop execution. The the failed document NoteID(s) will be shown again at the end and written to the status bar.
The 5 Simple Steps
- Select the document(s) to update
- Click your toolbar button
- Select the field to update
- Select the data type or action to be performed
- Select or Enter the new information (if prompted)
Limitations
- Only 1000 documents can be updated at a time
- All @Prompts are limited to 255, including values and text messages
- When updating multiple documents only the documents that are selected and visible (expanded) in the view will be updated. Notes needs to be able to navigate to the document in order to update them
April 25th, 2006 - 07:00
I just wanted to say: Thank you!.
Thanks for the tool. Thank you for constantly improving it and for sharing it with us.
It saves me my precious minutes every day.
April 28th, 2006 - 07:56
Thanks Voytek, it is comments like this that makes the work worth it.
May 31st, 2006 - 19:32
Hey Chad,
This Rocks !!!! Thank You
July 13th, 2006 - 05:13
Hi Chad,
just a little Extension you should think of…
…
RawValue := @If( @Contains( DataType ; “Name Multi Value” ) ; @PickList( [Name]; @GetField( EditField ) ); …
to see the actually selected Names in the Dialogbox.
And – of course – its an every days livesaver
July 13th, 2006 - 07:34
duh, thanks. Never even thought of that.
December 12th, 2006 - 12:34
Hey Chad, it’s great but my personal version looks like this:
… cut …
REM {Prompt for which field needs to be updated. Loop until a field is selected or ‘Cancel’ is selected};
@DoWhile(
EditField1 := @Prompt( [OkCancelList]:[NoSort] ; cPromptTitle ; “Select the field you wish to alter or enter a new field to add:” ; LastField ; “-NewField-”:@Trim( @Unique( List : LastField ) ) );
EditField1 = “” );
EditField := @if(EditField1 = “-NewField-”; @prompt([OKCancelEdit]; cPromptTitle; “What’s the name of the new field ?”; “”); EditField1);
EditFieldPromptTitle := “Change ‘” + EditField + “‘ in ” + cPromptTitle;
… cut …
I like the bigger box and the possibility to add a new field in one step
January 24th, 2007 - 10:35
Do you take bug reports? Actually I don’t know if the issue is with your tool or with a set of (possibly corrupted) documents – I’m going to be hunting down the profile document and wiping that out next to see if that helps. I use this in my toolbar all the time, but just today I’ve been crashing every time it starts making updates. Anyone seen this behavior before?
Notes version: Release 7.0.2 September 26, 2006
OS version: Windows XP 5.1
Client uptime: 0 day(s) 00:03:46
Error message: PANIC: LookupHandle: handle not allocated
…
@[ 1] 0×60177011 nnotes._Panic@4+417 (60ae0948)
@[ 2] 0x6000293d nnotes._LockHandle@12+317 (228,13e4a4,13e4b0)
@[ 3] 0×60009756 nnotes._OSMemGetFaultHandle@4+22 (60d2e3e0)
@[ 4] 0×60009801 nnotes._OSLockPool@8+17 (13e4f4,228)
@[ 5] 0x607dd446 nnotes._NSFNoteAddCloseHandler@12+54 (228,61b527c0,13e52c)
@[ 6] 0x61b572db nnotesws.DoCommand+539 (7434014,740a214,43)
@[ 7] 0x61708bb3 nnotesws._DeskComputeExtension2@36+467 (7434014,740a214,ed,1,7,13d928,1003f,0,0)
@[ 8] 0x617089da nnotesws._DeskComputeExtension@36+42 (7434014,740a214,ed,1,8,13d928,1003f,0,0)
@[ 9] 0x600b2ffa nnotes.CompGeneralContext::ExtensionProc+298 (e,ed,0,1,9,13d928,1003f,0,0)
@[10] 0x600b3535 nnotes.ExtensionProc::Execute+229 (7468f90,7468f20,2,8,a,13d928,1003f,0,0)
@[11] 0x600456b2 nnotes.AtFunctionNode::ComputeVariants+82 (7468fc4,746c1cc,2,0,b,13d928,1003f,0,0)
@[12] 0×60045697 nnotes.AtFunctionNode::ComputeVariants+55 (7469000,1,7462474,7469000,c,13d928,1003f,0,0)
@[13] 0x6008beab nnotes.$L36223+45 (746c178,746236c,746a924,74622d0,d,13d928,1003f,0,0)
@[14] 0×60505178 nnotes.AtWhile::ComputeVariants+152 (0,7434014,1,492,e,13d928,1003f,0,0)
@[15] 0x600458e1 nnotes.RootNode::ComputeVariants+81 (0,7434014,74459a0,1,f,13d928,1003f,0,0)
@[16] 0x600454cd nnotes.Compute::Eval+141 (740a214,13ee2c,74459a0,0,10,13d928,1003f,0,0)
@[17] 0x600b2cad nnotes._NSFComputeEvaluateExt@32+157 (7434014,0,13ee2c,13ec88,11,13d928,1003f,0)
@[18] 0x600b2bef nnotes._NSFComputeEvaluate@28+47 (7434014,0,13ee2c,13ee42,12,13d928,1003f)
@[19] 0x61b0e411 nnotesws._ExecuteMacro@16+529 (0,22b,0,0)
January 24th, 2007 - 12:05
Sorry, but I have no use for a bug report.
Is it a categorized view, is the field that is being updated the sorted column?
Please let me know if you find anything out.
May 24th, 2007 - 06:00
This seen to be a problem with R7.0.2 as I have the same behavior here. If I execute it with my R6.5.1 client (on the same box against the same database) it works like a charm.
Even if it does crash on a R7 client, it is a WONDERFULL tool that saves me a LOT of time.
November 21st, 2007 - 06:32
This tool is great!! I’ve used it since at least version 3.0. THANKS!
January 15th, 2008 - 14:41
Just wanted to say thanks. I, like many others, save so much time with this tool. I’ve used it for years. I had to google for it today because I was setting up a new workstation remotely and, of course, ran into an immediate need for my favorite toolbar button!
May 12th, 2008 - 21:11
Useful – but I also wanted to delete all traces of a field with @Unavailable so I modified the code in such a manner:
Change 1
REM {Data types|@Function execution};
DataTypesCombo := @Explode(
“Unavailable|@SetField(\”EditField[ef]\”; @Unavailable)$”+
“Integer|@TextToNumber( RawValue )$”+
“Integer Multi Value|@TextToNumber( @Explode( RawValue ; Separator; @True) )$”+
etc…
Change 2
REM {Based on what type of data is being entered different prompts will happen if any at all.};
RawValue := @If(
@Contains( DataType ; “Unavailable” ) ; “” ;
@Contains( DataType ; “Name Multi Value” ) ; @PickList( [Name] );
etc…
February 20th, 2010 - 15:06
Is it only me and my browsers, or is the code finally gone? Bummer, don’t know where I left my copy. Probably no more updates to this site …
February 21st, 2010 - 18:51
I have the code and I am sorry it is not showing up, I will fix it so it does appear.