Solved

Place notes not editable on WebClient

  • 23 June 2021
  • 9 replies
  • 242 views

Userlevel 2
Badge +5
  • Sidekick (Employee)
  • 7 replies

Hi all

Has anyone else faced the issue that the notes on the WebClient Place screen after an updated text show [object Object]? Furthermore the note type is missing.


A save attempt after modification will not save the changes.

Before Update, Note type is empty
Before clicking “OK”
After clicking “OK”

Looking forward for your answers.

Best regards:

Marko

icon

Best answer by Brian Maus 24 June 2021, 00:59

View original

This topic has been closed for comments

9 replies

Userlevel 7
Badge +22

Hi @Marko ,

 

Have you refreshed /cleaned your browser cache and able to re-generate this issue?

Userlevel 2
Badge +5

Hi @Marko ,

 

Have you refreshed /cleaned your browser cache and was able to re-generate this issue?

Hi @Saranga Amaraweera 

Yes I did, no impact.

Best regards:

Marko

Userlevel 7
Badge +22

Hi @Marko ,

 

Have you refreshed /cleaned your browser cache and was able to re-generate this issue?

Hi @Saranga Amaraweera 

Yes I did, no impact.

Best regards:

Marko

@Marko ,

 

Are you getting the same issue in different web browsers or is it specific to only one browser? 

Userlevel 6
Badge +20

Hi @Marko 

 

What is the FSM version you are referring to? Earlier, there was a bug in FSM 6 update 4 where inactive note types display as  {<note_type>}  in web client. Many thanks.

Userlevel 2
Badge +6

Hi @Marko,

 

We had this exact issue when upgrading from 5.7 to 6. We had this issue everywhere in FSM 6 where we had custom 5.7 screens that had *_note and *_txt tables. Or to put it another way - if the screen wasn’t the new “message board” display style of entry it wouldn’t work. This was quite a few screens in our case.

 

We fixed it this way (using place_note as an example):

 

If place_note.text_rtf was null we copied place_note.text to it.

Copied the entire TabItem for “Notes” from the baseline screen and replaced the 5.7 TabItem.

 

 

Userlevel 7
Badge +22

@Marko Found some community posts in which could be similar to this bug. Hopefully you would be able to get an idea about this. 

 

 

Userlevel 2
Badge +5

Hi @Marko,

 

We had this exact issue when upgrading from 5.7 to 6. We had this issue everywhere we had custom 5.7 screens that had *_note and *_txt tables on 6. Or to put it another way - if the screen wasn’t the “message board” style of notes it wouldn’t work. This was quite a few screens in our case.

 

We fixed it this way (using place_note as an example):

 

If place_note.text_rtf was null we copied place_note.text to it.

Copied the entire TabItem for “Notes” from the baseline screen and replaced the 5.7 TabItem.

 

 


Hi @Brian Maus 

Thanks a lot for your answer. I am pretty sure it will solve the issue - but I guess then the user can no longer specify the PLACE_NOTE.USER_DEF1 when adding a new note? Any chance we could get this working along the way with the new popup being opened when modifying the Text?

Best regards:

Marko

Userlevel 2
Badge +6

Hi @Marko ,

 

Maybe it does -- just never had to use it like that! If you’re flexible about not needing rich input this snippet uses a _tx table and works for userdefs. Kindly ignore the “View All” button which does nothing.

 

 

Userlevel 2
Badge +5

Hi all

@Brian Maus: Thank you so much for the input.

This is how it has been solved, but most of these steps need to be performed in the screen’s XML config:

  1. Change that tab <name> content with the suffix “Custom”: PlaceNotesCustom
  2. Hide the “_RTF” DB field and embed the “note” field into the listview.
  3. Create an _ALIAS table in Custom Metadata. Replace every iteration of the default table name “PLACE_NOTE” with the “PLACE_NOTE_ALIAS” (except) for the counter ID in the XML screen code.
  4. Change the “New” button to be no longer assigned to the name “addNote”, but replace it by just “add”.

Finally, this configuration allows you to also embed USER_DEF fields into these “Notes” tabs and to work without the RTF editor entirely. Thanks for coming up with the solution @ruben.maas!

Best regards:

Marko