Serializing with a script

[Warren Roberts]

Can someone help me.

I am working on an estimating database that once sold will convert the information to an order. My problem lies in that I cannot figure out how to serialize the work order # field with a script. I can easily serialize the estimate # when the record is created, but as we all know we write 10 estimates to get 1 job. so I need to have a script that will check the last order number and add 1 to it. I know it's probally simple but for now the answer eludes me.

Warren

[Lee Smith]

Use the Set Field Script Step.

SetField(WorkOrderID, EstimateID)

HTH

Lee

[Fitch]

Max(Self::OrderNumber) + 1

[Lee Smith]

That would be if he want to keep a separate number for the work orders. I perfer to keep the chain from estimate to invoice.

Lee

[LaRetta]

Hi,

I agree about keeping the chain between Work Orders and Invoices; however, since there are more Work Orders generated than Invoices, you will end up with holes in your invoice numbers.

I would prefer to keep the chain by referencing the Work Order# in a field within the Invoice and then generate sequenced invoice numbers. Just a thought.

LaRetta

[LiveOak]

I agree with LaRetta. Auditors get funny about gaps in the invoice number sequence. It is less important that the invoice number matches the estimate number, as long as there is a link.

-bd

[Lee Smith]

Hog wash,

A work order is an authorization to perform work. Therefore an Invoice would naturally follow.

An Estimate, or Request for proposal, well now, that is a horse of a different color and doesn't even need a number until it becomes a Work Order.

Lee

[Ugo DI LUCA]

No rule established for this IMO.

Surely depends upon each case.

you may have a Work Order splitted in several Invoices too...

You may establish some links in the line item, but it doesn't necessarily mean you need a serial for Work Order "linked" to the Invoice.