I am running into a problem when trying to insert “comment” sales lines using Scribe Insight. In NAV’s Role-Tailored Client, we can click to add a new sales line, put in a description (for example “Print this comment!”) and then remove the Type so it won’t look for an item number. This works fine and if you view the row in NAV Classic, it has a type of 0.
But if I try to use Scribe to put in a comment, it gives me “Type must not be [blank]”, EVEN if I specify type 0. They sent me this link when I asked for help:
However nothing they gave me to try fixed the problem. Eventually they settled on:
"This really isn’t an issue of Scribe being “broken” (as Support handles break/fix issues), but is regarding manipulating/designing the dts to work with NAV per requirements from NAV .
As noted in the article we sent you: “We have also had at least one consultant modify parts of the validation logic to look for empty strings in specific fields and conditionally execute the validation logic. That is not a solution we would outline here but a qualified NAV consultant could help you with this type of resolution to the issue.”
Does anyone here have any experience with this sort of thing? I would hate to have to pay for Scribe’s consulting when there are plenty of knowledgeable people out there who could probably help me out (Especially given that Scribe charges an arm and a leg for anything).