SPJS Table Chart and Note field

Home Forums SPJS Charts for SharePoint SPJS Table Chart and Note field

Tagged: 

Viewing 11 reply threads
  • Author
    Posts
    • #34557
      Phil Grant
      Participant

        Hi,
        I have some charts on SP2010 SPJS v.6 and I’m trying to rectreate them on SP2019 SPJS v.7 in a table chart, I’m not able to select some fields, I think the problem is that the missing fields are all “Note” fields?

        Is there a reason why I could select “note” fields in SPJS v.6 on SP2010 but not in v.7 on SP2019?

        Thanks,

        Phil

      • #34566
        Alexander Bautz
        Keymaster

          Hi,
          v7 is completely redesigned from v6 and I skipped note fields because I didn’t think it was relevant to use in a chart (didn’t think the table chart…).

          I have fixed is and have attached the script file below. Just unzip and drop it in your SPJS/CHARTS_V7 folder.

          I’ll include it in the next release.

          Alexander

        • #34581
          Phil Grant
          Participant

            Alexander,
            Thanks for the fix, I thought it was a bit strange.

            Phil

          • #34605
            Phil Grant
            Participant

              Thanks, that fixed it, one other strange thing I’ve noticed is that the label for the index field converts any spaces to the “+” sign when saving the configuration, is this the script or something to do with SharePoint?

              Cheers

            • #34613
              Alexander Bautz
              Keymaster

                Hi,
                Not sure which field are you referring to – add a screenshot if possible.

                Alexander

              • #34615
                Phil Grant
                Participant

                  I will add a screenshot tomorrow but it is all fields in the table chart, when you add a field any labels that have spaces get the spaces replaced with the + sign when the configuration is saved.

                • #34619
                  Alexander Bautz
                  Keymaster

                    I tested adding labels and cannot reproduce this issue – I’m using Chrome, which browser are you using?

                    Alexander

                  • #34622
                    Phil Grant
                    Participant

                      Currently using Edge but will try it on chrome as well and let you know.

                      Phil

                    • #34624
                      Phil Grant
                      Participant

                        I wonder if it’s an issue with SP2019 then.
                        I will ask our It support.

                      • #34642
                        Phil Grant
                        Participant

                          Here are a couple of screenshots showing the table header and the config page, when I remove the + from the label and use spaces the spaces are replaced by + as it’s saved.

                          This happens in both Edge and Chrome, I suspect that if it doesn’t do it for you then it’s probably something to do with our SP2019 instllation.

                          • This reply was modified 3 years ago by Phil Grant.
                        • #34647
                          Phil Grant
                          Participant

                            Alexander,
                            I’ve had some feedback from my IT support and they said
                            “We think that it matters which JavaScript encode function is used before the configuration is sent to SharePoint list.
                            SPJS creates a “escaped” JSON which is sent to a list.
                            We also found a workaround, instead of using ” ” (space) – use  ”

                            I used their suggestion and it looks fine now.

                          • #34652
                            Alexander Bautz
                            Keymaster

                              I’m not able to recreate this issue on my SharePoint Online tenant so maybe it is related to an on-prem 2019.

                              In any case I’m glad you found a workaround.

                              Alexander

                          Viewing 11 reply threads
                          • You must be logged in to reply to this topic.