Cityworks SQL Data Ingestion Research -- 2

Job ID: 40208548

Budget: $10 – $30 USD

I need a concise technical blueprint that shows exactly how to print in Cityworks environment at through SQL Server Management Studio. The goal is to make sure a field on the form "DUP. BAD CHECK “ L-If a Bad Check fee (L-BADCHECK) is attached to a case, it's owed. Status, type, etc. do not matter.

Same for L-DUPLCTE.

L-DUPBC - this is either or both a bad check fee and a duplicate fee from historic records (Pre-migration)

30 - BC

20 - Dupe

50 - Both (Rare, if it exists)

the Cityworks front-end application, then landing it in the back-end SQL database on a batch schedule.

You’ll be working with:
• Cityworks PLL (latest build)
• Microsoft SQL Server 2019 + SSMS

What I expect from you:
• A clear, step-by-step document that maps Cityworks (PLL) tables and objects involved in L-senddeclar 491498.
• Recommended method for extracting the data from the Cityworks UI layer (e.g., service requests, work orders, or custom reports) and staging it for batch loading.

• Advice on scheduling the batch job, handling errors, and rolling back partial loads.

Please respond only if you have hands-on Cityworks database experience; generic SQL answers won’t help here.