topic Re: Alteryx Server MongoDB - AMP Count,E1Count and No of Jobs formula in Alteryx Server Discussions

Alteryx Server MongoDB - AMP Count,E1Count and No of Jobs formula

pnaveen — Wed, 14 May 2025 22:16:47 GMT

Hi ,

I have an attached reference alteryx workflow previously designed by someone.I was going through and in the 2nd half, after the macros i see some new calculation designed and they are counts based on the fidlls POSPriority and RunwithE1. They are derived as AMP Count,E1Count and No of Jobs formula , not sure how they calculated these counts and formulas.If anyone knows about the formulas, please advice.

Also in the second part, how can i connect from a filter tool to 3 select tools without any selection of macros. below is the screenshot for your understanding and please advice, thanks

Re: Alteryx Server MongoDB - AMP Count,E1Count and No of Jobs formula

KGT — Thu, 15 May 2025 02:39:44 GMT

Those macros are just the CountRecords tool. Not sure why they are not showing up for you. You can just replace the black icons with the CountRecords and continue. Make sure that the connection string ID's are still the same on the join so that the correct fields are renamed.

Re: Alteryx Server MongoDB - AMP Count,E1Count and No of Jobs formula

pnaveen — Thu, 15 May 2025 03:54:11 GMT

Thanks for the response. I will use the countsrecords tool in the pace of macros.

I need some clarity of these derived fileds

1)AMP Count,

2)E1Count and

3) No of Jobs

I have unused filed like Status, POS Priority , RunWithE2 and _version, and timeinQueue, i want to know how these fileds are related to derive the other formulas

1)AMP Count,

2)E1Count and

3) No of Jobs

Basically i am trying to reverse engineer the formula or fileds for these 3 derived fileds or formulas. Thanks

Re: Alteryx Server MongoDB - AMP Count,E1Count and No of Jobs formula

KGT — Thu, 15 May 2025 23:09:18 GMT

Have a look in the select tools. Those fields are not calculated, they are just renamed counts.

The package you sent had the CountRecords in it, and so I can see the completed workflow. The package had the CountRecords Macro included though, which is possibly what caused your issue in the first place, if you've moved the workflow or something else that has broken the reference.

You do not need to calculate them, just put the count records back in.