Forum Replies Created
I have got this working….. sort of, the HTML table will populate with the lookup data but only if the lookup field is added to the Tab normally, with the normal field added to the tab the HTML table populates with the child values but if I remove the normal field then the HTML table stops populating.
Is this something to do with the triggering of the function only happening if the normal vlookup field is on the tab?
Thanks Alexander I’ll give it a try.
Works a treat, thanks for the quick update.
I’ve had some feedback from my IT support and they said
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.
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 2 years, 5 months ago by Phil Grant.
Thanks, tested and working.
I had a good mess around with the CSS stuff and inspecting elements with Dev mode and finally sorted it out, you examples helped me to sort it out so thanks.
One thing I’ve learned is that you can edit he CSS styles live in Dev mode to see what it looks like then put it in the custom CSS tab, I didn’t know that.
I wonder if it’s an issue with SP2019 then.
I will ask our It support.
Currently using Edge but will try it on chrome as well and let you know.
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.
Thanks, I’ll give them a try, unfortunately the “Stretch side by side fields…” didn’t do the trick 🙁
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?
Thanks for the fix, I thought it was a bit strange.