Panopea Consulting - iMIS Blog

[...] , it's pretty simple once you know the answer! You stick the first detail of the group into the Group Header and then set the Group Header to have "Keep Together" turned on in the Section [...]

[...] . Unlike in the Letters system, when you export from IQA, the export process strips out the carriage returns of fields such as CsContact.FullAddress. It strips it out of calculated fields too. This [...]

[...] above but then it is followed by this statement: update Counter set LAST_VALUE= isnull((select max(Trans.INVOICE_REFERENCE_NUM) from Trans),1),LAST_UPDATED=GETDATE(),UPDATED_BY='MANAGER' where [...]

[...] called asi_RebuildCounters. It is what is executed if you use the DBRepair tool to run the Rebuild Counters. That proc is missing a little bit of logic that will throw off the Invoice_Ref counter if [...]

[...] " display of products in the Public View Billing module is to display the products in product code order. Whose idea was that?! It ought to be Payment Priority, then Product Title, IMO, and [...]

[...] for an IQA query: Just like with the Word Integration system, aka Letters system, the export format iMIS uses is that the data is in a Word table. You know what the maximum number of columns [...]

UPDATE 07/08/10: ASI has given this issue a priority of HIGH. It was reported as SMR 216423. I came across a bug in the Rebuild Counter process that [...]

[...] affects iMIS 15 and only if you are using online events. (Am I remembering correctly that the Prepaid invoice created by iMIS would have the invoice reference number in it already? If not, then online [...]

[...] with the same invoice reference num. Turned out there were 24 orders sharing 12 unique invoice reference numbers. [...]

[...] The "out of the box" display of products in the Public View Billing module is to display the products in product code order. Whose idea was that?! It ought to be [...]