Receiving the following error - any ideas?

Nate@E

• Not all columns [750410017335172] exist in the mapping da981860-0f9e-4340-9e83-05d7461fbdd4.

This in the document builder feature. Was previously working fine. The mappings do not show any errors, I guess I could go column by column, but am I looking for a deleted column, or simply a column with a name change maybe?

This is when I'm trying to populate a PDF from the data in the row.

Lesa Weaver

Hello @Nate Ensor

We go that error message recently when we deleted a column in our sheet and then ended up adding it back with the same name. We decided it was looking at the column ID# and not the column name so the new column had a different ID# that wasn't mapped and the old column was still mapped.

We unmapped the old column and saved. Then we mapped the new column and that fixed the error.

Hope this helps!

Andrée Starå

Hi @Nate Ensor

I hope you're well and safe!

Strange! Is it connected to DocuSign?

If you haven’t already, I recommend submitting a support ticket through the new Smartsheet Support Portal.

I hope that helps!

Be safe, and have a fantastic week!

Best,

Andrée Starå | Workflow Consultant / CEO @ WORK BOLD

✅Did my post(s) help or answer your question or solve your problem? Please support the Community by marking it Insightful/Vote Up, Awesome, or/and as the accepted answer. It will make it easier for others to find a solution or help to answer!

Nate@E

Yes, connected to DocuSign. I've put in a ticket in the support portal as well as in DocuSign.

Andrée Starå

@Nate Ensor

Ok. My guess is that it's something with DocuSign that gives that error.

Feel free to update us when you hear back from Support.

Lesa Weaver

Hello @Nate Ensor

We go that error message recently when we deleted a column in our sheet and then ended up adding it back with the same name. We decided it was looking at the column ID# and not the column name so the new column had a different ID# that wasn't mapped and the old column was still mapped.

We unmapped the old column and saved. Then we mapped the new column and that fixed the error.

Hope this helps!

Nate@E

Yes, thank you for adding this (to help me know I'm not crazy!). This is essentially what I did as well. The hard part is getting to this conclusion as there is no indication as to what field is not mapping correctly. To make matters worse, the fact that it still flows correctly up to docuSign for the person signing, and doesn't show as blank until after they sign... is another difficult problem to diagnose or even recognize as a problem if you are not really looking at the document, just filing it as in our case.