Potential Issue with 'AtmStrategyClose(string atmStrategyId)' Command in Ninjascript

[bltdavid]

If you need to get the realized Pnl your workaround would work based on the old way in NT7 that the close happened.

So, the NT8 help page is really screwed up then, isn't it?

Just admit it, Jesse, the NT8 help page is contradictory and
needs to be fixed.

[NinjaTrader_Jesse]

Hello bltdavid,

If you have suggestions for the help guide please feel free to provide that in the suggestions and feedback sub forums.

[bltdavid]

Hello bltdavid,
If you have suggestions for the help guide please feel free to provide that in the suggestions and feedback sub forums.

Done.

Do your job there, or do your job here, doesn't matter.

You need to check your ego and study that help page.
Please verify the content is incorrect (just as I have told
you, in this thread, several times) and submit a ticket to
get that page fixed.

It's a simple task.

Many support folks will happily submit a ticket, and then
report the tracking number back to the main thread
discussing the issue.

Why you haven't done that here (and don't seem to want
to do that) stands in stark contrast to the superior support
provided by your peers.

Now, please get it done.

[bltdavid]

I just wanted to try and help clarify that this is expected that a 0 value is seen in this use case. This is tracked internally under the ID NTEIGHT-13996.

Jesse, let me ask you this.

In NT7, the 'close' followed by 'get realized profit' worked correctly.

But now, in NT8, this sequence no longer works correctly.

Ergo, this is a bug in NT8.

And now, we find out you have an NT8 issue for this bug.

Yet, to you, this is not a bug.
You now consider this bug the expected behavior?

Why is that?

-=o=-

Furthermore ...

You can't seem to admit in any way that your support in this
thread has been poor. You have failed to address any of the
discrepancies that have been pointed out to you.

Want an example?
You have an NT8 reference sample showing 'get realized profit'
being called after the position is flat, but you can't see the
significance of this revelation, nor how it made your early
answers suspect. You won't even address how this implies
the OP's code was completely correct, and that your claims
otherwise were non-supportive.

Yes, I apologize, I said your answers were 'crap' before.
I beg your pardon, I meant to say 'extremely suspect'.

And now, here we are.

This is a bug. Always has been. It still exists today. And yet,
in this thread, circa 2023, you're trying to say this defective
behavior is now the expected behavior?

That is extremely suspect, don't you think?