Dex - Dexterity and IntelliSense: It's time to vote!

Yesterday I presented some arguments for IntelliSense implementation in Dexterity. If you are an ISV or application developer who spends a lot of time developing Microsoft Dexterity applications and working in the Dexterity environment, you may certainly appreciate the benefits of having intellisense embedded in the sanScript language. Take this sample muck up of the Script Editor window:

As a result of this, I have opened a Microsoft Connect product suggestion to have this feature implemented, but it cannot be even considered if YOU the reader don't take 1 minute of your time to vote on the suggestion. So, if you are reading this now, please click on the link below the image (or on the image itself) to cast your support for this suggestion.

Microsoft Connect product suggestion 570553

[Ed:] If you have problems accessing the link, visit to associate your Windows Live ID and create profile prior to voting.

The Microsoft Dexterity development community would also appreciate if you could join the cause, even if you happen not to be a developer. Now, go vote and tell everyone you know about the case number!

Until next post!

Mariano Gomez, MVP
Maximum Global Business, LLC


Jivtesh Singh said…
The link doesn't seem to be working for me. I tried logging in an searching but found 0 results
Anonymous said…
Excellent, Mariano. I've placed my vote in the affirmative!

Take care,
Ron Draganowski
Beat BUCHER said…
Hi Mariano,
This is a great initiative. Although I'm not developing yet in Dexterity, I always welcome and encourage stuff that makes the developer's life easier :-)
Keep up with such bright proposals.
Have a great day,
Mariano Gomez said…

Chances are you will need to first register with Microsoft Connect at

Please let me know if you have further questions.

Keir Pollard said…
Great suggestion, Mariano. If I could add another suggestion to this feature, it would be code snippets. Dexterity is fairly verbose, and most code consists of a limited number of standard patterns. For example, you will often use a variation on this same chunk of code for range operations on tables:

release table table_name
set field1 of table table_name = value1;
range start table table_name by table_key;
set field2 of table table_name = value2;
range end table table_name by table_key;

get first table table_name by table_key;
if err() = OKAY then
{Not OK}
end if;

It would save a great deal of typing if you could just select and drop in this snippet, and substitute in the appropriate table names.

Same thing for many other constructs in Dexterity, such as the standard Save_Record scripts, (L) Temp Control Number scripts, record and window note scripts... and everything else detailed/sampled in the Integration Guide manual.

Of course, with this snippet library you would want to be able to add and remove snippets (for proprietary documentation standards, etc).

Cheers, and thanks again for your blogging!!
Jivtesh Singh said…
Not sure how, but I was able to get through using IE. Earlier I was using Chrome.
Mariano Gomez said…

I would agree. Please update the suggestion with your note and code snippet.

Janakhiram said…

Just voted for your cause though I'm not into dex development. I can understand the value add you are trying to bring to dex development.

Good Luck

Mariano Gomez said…

Much thanks. In fact, any support you can rally around this issue I would much appreciate it. I am personally calling and soliciting people directly.


Popular posts from this blog

Power Apps - Application Monitoring with Azure Application Insights

eConnect Integration Service for Microsoft Dynamics GP 2010

Troubleshooting the Microsoft Dynamics GP 2013 Web Client - Part 3