Thanks in advance for any insight. Here is the issue:
I have a form within which one of the fields is an editable rich text field for attachments. The field is named ElecAttach. This field suddenly, (well, I am not sure when the issue arose but it has just been brought to my attention), has become inaccessible. It had a hide/when formula, which I removed for testing purposes. It still does not show up. I moved it to an entirely different section of the form, still no luck. I copied the entire contents of the form to a new form, and ran an agent on the document I am testing with to assing the new form name to it. Same result. Next, I reset everything back to original. I left the ElecAttach field where it was, and renamed it. It appeared without issue. I ran an agent to assign the ElecAttach contents to the renamed field, which made that renamed field inaccessible. I reset the renamed field back to “”, and it re-appeared. This behavior is not limited to this document. I performed the same test on several other miscellaneuos documents with the same result. I finally ran an agent to refreshalldocs, which produced no solution. I am baffled. I am trying to perform tests of deduction, but all I have come up with is that the contents of the field ElecAttach are inaccessible throughout the database…and if you assign the contents of that field to another field, that field also becomes inaccessible, no matter which document you do it with…so it does not seem to be an issue of a corrupt attachment. The ODS version of the database is 41.
I think that Rich Text Fields keep all their properites, even if you delete the field and then re-add it. For some reason, it may have the hide feature still with it, and thus you cannot see it. That is my 2 cents anyway… John
Thanks for the responses. I tried copy->paste first, then also tried creating a brand new field of the same name, with the same properties and no hide/when formula. There are only attachments in the field no text. It is strictly notes client only no web.
Not only did I create a new field, but again I created a new field with a different name, (which initially appeared without issue) and assigned it the contents of the ElecAttach field via an agent, which produced the same behavior for the new field and that behavior was not limited to a single document, but all the documents that I checked…
Another test…I placed another field alongside the new ElecAttach field…a computed text field primed with “hello”. No hide formulas. When previewed, it did not appear. I removed the ElecAttach field, and the computed text appeared without issue. Add the ElecAttach field back, and the computed text is gone. Somehow, the hide/when formula is being maintained? Strange, especially considering that the original hide/when formula is based on a field not being set to “Yes”, and that field is, indeed, set to “Yes”…also, as previously mentioned, you can create an entirely new field, and assign the contents of the ElecAttach field to it, and the same result is produced…for all documents.
NotesPeek helped out there was a portion of an old hide/when formula which apparently “stuck” to the field and caused the issue. I can work around that thanks alot!
The problem you are describing sounds like a hide-when formula which is “sticking” because it is within the rich text itself. See my post Rich Text 101 - Hide-When formulas for some explanation, plus the rather more entertaining Mike Midas case file Carrying Concealed for thoughts on the matter.
Also, iIf you need to go that direction, our Midas Rich Text LSX can fix up the problem very simply.
Remove the HideWhen formula for that RichText Field.If still you have the same problem, delete the field and save the form. Create another richtext field with same name as the deleted one.
If at all, if this Rich Text Field need to be diplayed on a condition, then better add this rich text field under a section (with hide when condition applied to this section) and a button in next row (code under it to open the rich text content in a subform or form with some key information as header, inherited from this main form) so that the button and the section will appear as needed.