We are currently in the process of creating configurators for one of our departments. The initial intent is to use the configurators in Quote Entry to generate pricing and details, and then to use some of those variables in the Quote Worksheet that we will send to the customer. To do this, we tie the QuoteDtl table to the PCInputs table in our report builder, and we call on the InputName and InputValue fields from the PCInputs table. For the most part this works fine, except we are running into a character limit (seemingly 50) for the InputValue field so we are extremely limited in our ability to provide adequate descriptions on the Quote Worksheet.
Almost certain this is not an issue with our report builder as we have not run into this limit before with other fields, but has anyone else encountered this problem? I’ve looked for a way to increase the character limit, but can’t find anything.
Tried making it an Editor field, but still getting the same result where it is limited when I print the report. And have confirmed with a BAQ that the PcInputValue.InputValue field is only storing 50 characters.
Ah I see what’s happening. The PcInputValue table is based on a view of the PcValueSet table, where configuration data is stored in XML format. I hadn’t realized it only stored 50 characters.
What I would do is add a line to your configurator Document Rules, and copy the value of your editor input to either a UD Field added to OrderDtl, or to an unused Comment field (OrderDtl.OrderComment, PickListComment, etc.). Then just reference that field from your SSRS Report.
Edit: QuoteDtl.QuoteComment, etc. Sorry, I use configurators in Orders way more often.
If there are values that you want to use regularly outside of the configurator I typically copy them out to either existing fields or user defined fields that I have added. For example if “color” is something you use regularly I would copy that out. Unless it is a small dataset, if a client feels that they need just about everything outside of the configurator I encourage them reanalyze their processes as that is rarely (being blunt, never) the case.