{dialog.object}.argumentValue bug

[DVD528]

Re: {dialog.object}.argumentValue bug

Not sure if it's best to revive an old thread or start a new one, so for now I'll keep it here since it has all the information related to the problem already.

Has anyone else reported this same problem? We use the {dialog.object}.argumentValue in a large amount of our components, and we have a large number of components to start with, some of which are very lengthy. The only solution would be to implement Davidk's workaround, which would be to insert every argument we have into a control using =:ArgName, and then use getValue rather than argumentValue, which would take a very long time to do since we would have to find every place we've used argumentValue (from client-side functions, to javascript returned by xBasic, to javascript actions, etc.), so we've opted to wait for the next update of Alpha, which (according to iRadiate) looks like it already contains a fix for this. It's been a trade off so far of debating on just biting the bullet and re-working the entire project in every place that contains the argumentValue function, or waiting for the update, and we didn't know which one would be quicker. As far as we know, this would be the only solution apart from waiting for the update, unless anyone else has another option.

Does anyone have any idea when the next official release is (since we don't want to deploy a production environment to a pre-release build)? This seems like a pretty significant bug, since it effectively breaks the function by causing it to return "undefined" in any components that existed during the upgrade to the version that contains the bug (3670_4684), so I'm surprised there hasn't been a bug fix release for it yet.

[DVD528]

Re: {dialog.object}.argumentValue bug

Just finished talking with Alpha, and they have found what the problem was, and also given code to put in the onRenderComplete event to patch the function until the next release is live.

To anyone else experiencing this bug, apparently the bug causes the normal accessing of an argument value by the correct case (for example "TestArg") to not work, and instead you have to access it through all lowercase (for example "testarg"). They have already altered the function so that in the next version, you can either access the argument by all lowercase or all uppercase, so if you change it to all lowercase in the current version, it will still work in the next version. Alternatively, if you are like us, and have many many different places where you use argumentValue in many different components, you can put the following code in the onRenderComplete client side event, and it will patch the function so the existing case (like "TestArg") will work correctly again:

{dialog.object}.argumentValue =  function(argName) {
	if(typeof this.stateInfo == 'undefined') return null;
	for(var name in  this.stateInfo) {
		if( name.indexOf('__args_') == 0) {
			if(name.substr(9).toLowerCase() == argName.toLowerCase())  {

				var argVal = this.stateInfo[name];
				if(typeof argVal == 'undefined') argVal = this.stateInfo[name.toLowerCase()];
				if(typeof argVal == 'undefined') argVal = this.stateInfo[name.toUpperCase()];
				return argVal;
			}
		}
	}
}

Hope this helps anyone else having the same problem. Glad it's finally resolved!

Many thanks to Alpha for their help in this matter, and the patch to fix the function.

[CarlMPearson]

Re: {dialog.object}.argumentValue bug

Looks like the bug is still there or resurfaced.

All I get is "__notSet__" as the argument values.

The component has been running for 18 months, but after a re-publish, the arguments are not being passed.

So far going all uppercase or all lowercase hasn't worked, either. I may have to figure out my own way of passing arguments.

v12.4.4.4 Build 4346 Addins Build 4889