Error on my dashboard page

Forums SPJS Charts for SharePoint Error on my dashboard page

Viewing 4 reply threads
  • Author
    Posts
    • #32252
      nk.franklin
      Participant

      Hello Alexander,

      Since the last infowise upgrade on our production environnent, we have this error on just one chart on our dashboard page.
      The chart is not loadind.
      I first thought there were somme change on internal name of some field during infowise upgrade.
      But seems like all the fields are ok on Datatable fields.
      Can you please take a look a this and help us?

      Sincerely,

      Attachments:
    • #32255
      Alexander Bautz
      Keymaster

      Hi,
      It is hard to tell what could cause this “unknown error” message. I’m not sure how updating infowise might have change your list so I’m not sure where to start there.

      Could it be that someone have changed one of the fields in the list, or maybe a lookup column has somehow been corrupted?

      Does the same error occur if you try setting up a new simple test chart with the same list as source?

      Alexander

    • #32257
      nk.franklin
      Participant

      Hi,

      I have on the same page other charts setting up with the same list as source.
      And these charts are working.
      There must one or 2 fields on the chart who is corrupted.
      Let me try to rebuild the same chart by adding field one by one and see what field cause the error.

    • #32259
      nk.franklin
      Participant

      Hi Alexander,

      It’s the Associated Items Summary Field who is getting the error.
      I don’t knwo why.
      I created a calculated field equal to Associated Items Summary Field.
      And replace the second by the first on chart.
      and it’s working now.

    • #32261
      Alexander Bautz
      Keymaster

      Hi,
      I’m not sure what could cause this – maybe one of the records in the list contains illegal characters in that field – this can sometimes happen when copy-pasting from word or other sources.

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

      Alexander

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