* Fixing UDF

[Ron Melby]

even the zip is too large. It is juat a screen, dont understand it. Nevertheless

Imagine that I have just ran the UDF plugin by tatewise.
SO...
I select a UDF Field, and get to the all tab to find it in detail.

Oh, look. I have the note field at the wrong level (I know this because I know it, not because the software helps me) Move it to the right level? nope.Easy enough anyway, copy the bad note field to the correct place, and delete the UDF, but how? right click? nope. Delete the entire source and rebuild it? CATASTROPHISCHE!!!!! NEIN!!! Too many parts to remember.

Fix it with a word processor? Seems to be the only way. Am I missing some fundamental thing here? Go directly to the problem, in FH and easily fix it. How?

[LornaCraig]

See how_to:handling_unrecognised_data_fields|> Handling Uncategorised Data Fields (UDF)
At the end of the section it says:

To delete UDF, select the desired fields and press the keyboard Delete key. In the Result Set of the UDF List Plugin, select any from the first column UDF Item, and Delete. There will be a warning message before confirming with OK. If after checking the effects, you change your mind, use Edit > Undo Delete Selected Data Items BEFORE closing ƒh.

[tatewise]

Also after moving the text to a valid Note on the All tab, just select the * UDF field and hit the Delete key.

I am fascinated by how many complex ways users can think of to delete an item, but rarely think of the Delete key

[Ron Melby]

I am constantly astonished at the inconsistencies in the methods of execution and interfaces in this software and the notion that anyone would have to read thru industrial bowls of spaghetti to do what should be simple intuitively obvious tasks. When one has worked some 10 years on building the tree, it is not a cause for marvel that they are reticent to push a delete key on any part of a complex transaction given that the murk of these various ways of executing transactions, many of which have extremely unintended consequences in the underlying file.

Nevertheless, thank you tatewise, there was no doubt that was in the stuff somewhere.