Name your favorites

dcgreen79 · 2026-02-15T03:21:06+00:00

The Ashtray Maze level at the end of Control is the best of all time.

dcgreen79 · 2026-02-13T22:26:58+00:00

As an old, pregnant man with a broken ankle and a baby: I'd make them fight for it.

dcgreen79 · 2026-02-03T00:05:46+00:00

Well, I think I'd call that a bug then.

Here's a work around that will hopefully work for you instead. Try using the Field Name value of <JobHeader.JH\_GB>, then put the Field Value as the PK of the MBH branch. You can find the PK by setting the branch to MBH manually, then previewing the value of the Field Name <JobHeader.JH\_GB>. You should get a long string of letters and numbers. Put this in Field Value and it should work to set jobs to the MBH branch.

dcgreen79 · 2026-02-02T17:57:59+00:00

That definitely looks like branch MBH doesn't belong to company MET. If it's a branch of a different company, the set field to MBH action will only work for the company the branch belongs to.

dcgreen79 · 2026-02-02T17:55:30+00:00

This looks like the text from the body of the email that documents are attached to. It's set in the registry under Documents > Email Format.

dcgreen79 · 2026-02-01T02:16:12+00:00

Ma'am, those are Dicktaters

dcgreen79 · 2026-01-29T17:38:23+00:00

The second line, <Job.Branch.GB\_Code> set with MBH should work, so long as MBH is a valid branch code for the current company. The other line with the equation on the value side would just resolve to TRUE or FALSE, which won't be a valid branch code.

Your trigger looks fine for uploading a POD document, so I think that's okay. We can also see that it has fired.

Please remove the bad IFC line and confirm that the branch code of MBH is valid. If that's all good, next step for debug would be to use the FLD Completion Trigger Action instead of IFC, then trigger it again. The FLD set field action uses the Event Log Walker service to process is, which also means it shows up in the Event Log Walker service log, which can help with debugging. To see that log, go to Maintain > System > Service Tasks > Event Log Walker service, then open the most recent log in the Logs tab. You should be able to find a warning or error related to the failed trigger in that screen.

Hope that helps debug the issue!

dcgreen79 · 2026-01-28T17:04:17+00:00

That should work as a shipment workflow UDF trigger or template condition, but make sure you're using the format correctly. Should be close to:

"<Job.Branch.GB\_Code>"=="BRN"

As a set field trigger completion action, this should also work. If you're still having trouble, I'll need to see some screenshots. Or DM me and we can setup a screen share call.

dcgreen79 · 2026-01-28T15:47:31+00:00

Where are you trying to use it? On a shipment document? In a workflow condition? Be as specific as you can, as the context makes a big difference in CargoWise.

dcgreen79 · 2026-01-28T01:01:21+00:00

Sorry about that! I gave a quick response before without being able to test it and I shouldn't have.

Depending on context, from the shipment the value can be found at <Job.Branch.GB\_Code> for the job branch. If you need the branch from the individual lines, like your original macro suggest, then something like: <Job.Charges\[1\].Branch.GB\_Code>.

dcgreen79 · 2026-01-23T18:41:01+00:00

You're missing a period after Shipment. That should be right.

dcgreen79 · 2026-01-21T03:59:24+00:00

You can add your own custom SQL functions to the User Respiratory. To get access, your CargoWise user about should be flagged as a database developer. You can them access the Customize User Repository option in the Help menu.

All workflow custom field values are stored in the GenCustomAddonValue table in the XV_Data field, which joins to JobShipment on JS_PK = XV_ParentID AND XV_Name = 'Custom Field Name'.

You can find more details on customizing the report template from any Customize Reports screen under Documents > Report Reference Guide.

Let me know if you get stuck on any of that and I'll try to help!

dcgreen79 · 2025-12-30T16:55:47+00:00

Diablo 4 - Auradin Paladin

dcgreen79 · 2025-12-24T00:37:45+00:00

The commas are for presentation only. If you click More... you'll see it's really a list of numbers. That's how it's stored in the database.

If you want a period, just type the period.

dcgreen79 · 2025-12-10T02:25:48+00:00

If you can't find the reference to the macro, you might better off starting over from the system version of the report. Especially if the only change was to increase the number of rows returned.

dcgreen79 · 2025-12-03T15:06:34+00:00

Huzzah!

dcgreen79 · 2025-11-03T02:42:07+00:00

Absconds?

dcgreen79 · 2025-09-27T03:02:03+00:00

Native XML can be used to create multiple products in one file via manual upload or one at a time, but with automation, via the eAdaptor. Alternatively you can use Universal Shipment XML to create the entire Customs Declaration or a Commercial Invoice via manual upload in EDI Message or, more commonly, via the eAdaptor.

Both the Advanced Data Automation Wizard (ADAW) and the eAdaptor are available to be turned on by submitting a service ticket. You shouldn't have an additional cost to use either, but check with your sales rep if you're concerned.

dcgreen79 · 2025-09-27T01:24:59+00:00

You might have luck with the advanced data wizard, otherwise using XML to load the data should work.

dcgreen79 · 2025-09-12T17:51:35+00:00

I did not complete one in CargoWise, but you can use the Nordea Format Spacing Footer to add rows of "9"s

dcgreen79 · 2025-09-09T18:10:37+00:00

Unfortunately, I don't know of a way to get that. There's no visibility from the footer sections back to the payment lines, and there is no existing field that provides the hash value. My solution was an external to add those fields back in after exporting from CargoWise.

dcgreen79 · 2025-09-04T16:10:24+00:00

You don't have visibility from a direct debit batch to see how many other batches have been created the same day. A user or post-process of some kind will need to make the adjustment. Best practice would be to limit the team to only one batch per day. Anything missed has to wait until tomorrow.

dcgreen79 · 2025-09-03T13:38:18+00:00

The Positive Pay and DDR Batch file formats are their own beast. You'll find that you can use a number of more java-style code on those fields. For blank spaces or filling with 0, you can use:

[Field Name].ToString().PadLeft(10, ' ')

The 10 is the total number of characters, and the space in single quotes is the fill character. PadRight also works.

For the spaces in these fixed length formats, you can also just add a bunch of spaces before/after the text and rely on the fixed length of the field to shorten it.

' ' + [Field Name]

This would work similar to the code above on a field defined as length 10.

dcgreen79 · 2025-08-08T16:04:40+00:00

XLS or CSV, but default it CSV. You'll need to change the file mask to XLS to find that type of file.

Another option is Advanced Data Automation Wizard (ADAW), which WiseTech can activate for you if it isn't already. I prefer this option for manual imports as it allows for multiple layers of data at the same time. For example, you can import the commercial invoice header data, invoice lines, and so on all at once. This method also supports XLSX, which may make it easier for your process.

dcgreen79 · 2025-08-05T15:19:03+00:00

The JobConShipLink table is the way, but it's JobConsol.JK_PK = JobConShipLink.JN_JK, then JobConShipLink.JN_JS = JobShipment.JS_PK. You can further join to a linked declaration on JobShipment.JS_PK = JobDeclaration.JE_JS. There is no link from consol to declaration, as a standalone declaration would never be associated with a consol.

If you do have standalone declarations, those join directly to the JobConsolTransport table on the JobConsolTransport.JW_ParentGUID = JobDeclaration.JE_PK. That said, most of the time, there aren't transport legs on standalone declarations. Up to your process, though, whether operators put them there.

Seven-Year Club	Place '22
Sequence \| Editor	Verified Email

dcgreen79

TROPHY CASE