Hello Everyone,



I am developing a word document for invoice creation. This word doc is uploaded to a web-based program called SAGE Intacct.

I have a table that has ITEMID and ITEMGLGROUP that functions similarly to SAGE Intacct.

When I run my attached word document through the program, NEXTIF created a blank row at the end of the table if the last ITEMID entry has a ITEMGLROUP that was skipped using NEXTIF.

If that last value is not skipped, the blank row is not created.

Unfortunately, Macros and/or VBA is not possible due to SAGE Intacct requiring DOCX. SKIPIF also does not seem to work.

I believe that last row is being created due to NEXTIF. I have attached 3 documents, my excel, word, and a screencap of the pdf I see as a result.

If I were to add a NEXTIF when GLGROUP = "", then I see something similar to the below forum post with only the field names displaying: [URL="https://answers.microsoft.com/en-us/msoffice/forum/all/mergefield-nextif-output-of-last-record-displays/db495d17-af9b-4d4e-9ae8-ada40049cd4e"]

XERO is an accounting software similar to Intacct, so hopefully the above link helps give another example of what I am trying to do. TableSort seems to mix my data too much as the lines are in a specific order.
My goal on this project is the following;
Skip GLGROUP 21, 24, and 25, and populate a separate table for them.

This is due to GLGROUP 21 being paper towels, GLGROUP 24 being Plastic silverware, and GLGROUP 25 being paper plates. Ideally group 21 and 25 on the same table, with GLGROUP 1-20, 22, 23, 26-30 on the first table, 24 on the second table, and 25 on the third.

Please let me know if using NEXTIF is a roundabout way of doing something more simple.

Thank you for the help!
-Harry

Attached Images

Output example for WEB.png (11.8 KB, 7 views)

Attached Files

	Item Example for WEB.xlsx (9.5 KB, 0 views)
	Table output example for WEB.docx (27.1 KB, 0 views)

Look at the options discussed in the Microsoft Word Catalogue/Directory Mailmerge Tutorial thread at the top of this forum: https://www.msofficeforums.com/mail-...-tutorial.html

__________________
Cheers,
Paul Edstein
[Fmr MS MVP - Word]

Hello Paul,

I took a look at the fields and learned more about how the fields work. It seems that {MERGEFIELD TABLESTART:ENTRIES} is a custom mergefield that is not compatible with many of the native fields in MS Word. (VIA Sage Intacct Dev team)

Unfortunately that means I may just have to wait for a new release from the developer side that fixes the bug. Thanks for responding anyways!

P.S. Many of your and Graham Mayor's posts helped me learn the basics of how mergefields work. A big lifesaver on a majority of what I had problems with, so thanks for that!

A field like {MERGEFIELD TABLESTART:ENTRIES} tells me you're using a 3rd-party application, such as Conga Salesforce. Accordingly, this isn't a Word issue as such and you have to work within the limitations of that application.

__________________
Cheers,
Paul Edstein
[Fmr MS MVP - Word]