TableExport API strips RecursiveTable dice references on table import from Excel

I've created a table in Excel with line items like: !import-table --Name-Of-Table --hide !import-table-item --Name-Of-Table --The party encounters **[[1d2]] Ankheg(s)** --5 !import-table-item --Name-Of-Table --The party encounters **a Basilisk** --2 !import-table-item --Name-Of-Table --The party encounters **[[1d8]] Needle Blight(s)** --4 When I copy and paste that list into the chat window, everything looks exactly as it should. But when I hit enter and the table is created the line items are modified to read: The party encounters **$[[0]] Ankheg(s)** The party encounters **a Basilisk** The party encounters **$[[0]] Needle Blight(s) What am I missing? Does the TableExport API not play well with the RecursiveTable API on import? I've tried removing the ** and the (s) but that does not fix the issue.

You need to escape the brackets like this example: --<%%91%%><%%91%%>1d8+1<%%93%%><%%93%%> Trolls (Instead of --[[1d8+1]] Trolls) Otherwise the API will process the roll that you are sending before the API creates a table item from it.

Well, once again, you save my bacon. I knew it had to be something simple I was missing. I need to find a list of those character replacements and tape it to my wall or something. Your help on this and my other macro issue is going to save me many, many hours of repetitive data entry. Thank you so much.

No sweat! I'm not positive, but I think those particular escapes are specifically for that script; in general for roll20 you'll just need HTML entity escapes. In the Macro Troubleshooting Wiki page  you'll find most of the ones you will ever need and when to use them ("}", "|", ",", "&"). And square brackets are "&#lbrack;" and "&#rbrack;".  Also if you ever need to convert tables that you already have to the import table format automatically there is an Excel Macro  for that as well!

They're specific to TableExport. It wasn't originally intended for human consumption so I used something that was unlikely to show up in a table row.

Ok then. I feel a little less stupid. I’ve done plenty of HTML and played with cgi scripting and JavaScript some so I have some experience. Makes me feel a little better that there’s proprietary stuff I just haven’t learned yet and it’s not me just forgetting stuff. I cannot express how excited and grateful I am to be building tools that will simplify my DMing tasks. So much to keep track of especially since I was using an established module and my party just decided they didn’t want to go back to town and went completely off-map. They’ve resisted all my attempts to get them back to Phandalin so now I’m home brewing my butt off. Thanks again. And thank you “The Aaron” for building these scripts. Genius-level work!

Hahahah! No problem! =D Time to start dropping in those refugees from Phandalin, and a surge of Dark Elves coming to take advantage of the forge and reek havoc in the path of the PCs... And then perhaps something truly awful gets wind of it (nice tentacles friend, does it make eating hard? =D).  I figure a problem not dealt with by PCs can always fester and worsen... =D

Good advice. I like the dark elf angle. Will keep that in mind. Have already introduced the consequences of inaction as a concept. I was kind of weaving Lost Mine and Icespire Peak together with a heavy emphasis on Icespire. Well, they decided Phandalin was too dangerous to return to so they saw Leilon on the regional map and said, "we're going south to Leilon" and inside I was screaming, "Noooooo!" We'll, they thought Phandalin was dangerous. Wait 'til they get a load of the ruined city of Leilon. I've already introduced a new story arc to give them something to do and woven elements of it back into the lost mine and icespire storylines (like the Redbrands are now a regional threat instead of just local to Phandalin). Some serious tap dancing though. I've been DMing less than a year and I've never had to build maps or create my own tools. I've just spent a crapton of money at DnDBeyond and on Roll20. (I was always a player back when I was playing... in the late 80's...) <bleep> just got real though.