Input page Nav2009

DavideVD

Hi to all,
as you have seen, running Nav2009, some old code is now "obsolete".

My question is:
How can I realize a page with the same behavior of dialog.Input command in NAV5.0 (now unsupported)? ](*,)

Ty very much

Belias

it all depends on what you want to do: what is the need of having it in the original form?
was the original form a list or a card?(if card, just add a textbox)
how the user make the dialog pop up?(validate, assistedit, onpush)
what do you want to do with it?

DavideVD

I want to simulate the page of input work date. I'd like to have the same appearance and result.
In previous version of Navision you could use the command dialog. input (i.e windows.INPUT(par1...parn)) to let the user isnet a value, without using a form.

Now, in Dynamics 2009 SP1, this function is Obsolete (like SHELL)

What I have in mind is a simple page with 2 button (If possible in the lower part of the page) with fixed dimensions (IF possible) and an INPUT field in the middle...nothing more
Thank you

PureHeart

Davide have you though about client add-in?
developing an easy add-in to pop up an input message would be pretty easy...

Belias

the role center page is always open when using RTC, so, why don't click then top-left button "microsoft dynamics NAV", Set work date... ?does the users change the workdate so frequently??
P.S.: the add-in solution is more fun to do

DavideVD

the role center page is always open when using RTC, so, why don't click then top-left button "microsoft dynamics NAV", Set work date... ?does the users change the workdate so frequently??

This was an exemple of the result wanted :shock:

PureHeart (nice nick ),what do you mean with " client add-in"? Something outside navision to insert a simple value? :-k

Is there nothing integrated in navision page or other stuff already supported?

PureHeart

Thanks

Is there nothing integrated in navision page or other stuff already supported?

Not that I know...client add-in may sounds difficult but they are instead very easy and the idea is that they will help you to overcome all the limitations of NAV / RTC as this one...so I recommend you to learn how to use them!
Here you can find all the info...
http://msdn.microsoft.com/en-us/library/dd983815.aspx

Belias

You can also create an unbound card page, with a single textbox with a variable, in onopenpage you populate the variable with workdate, and in the onclosepage, you modify the workdate based on the new value of the variable.
about the bottom buttons, i guess that you can play with InFooterBar property of the actions, but i've never used it, just try it!

ara3n

MSDialog is dotnet Microsoft.VisualBasic.Interaction.'Microsoft.VisualBasic, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
make the RunOnClient property to true.

MyValue := MSDialog.InputBox('Please Enter Data','Title','',50,50);

Message(MyValue);

PureHeart

ara3n wrote:

MSDialog is dotnet Microsoft.VisualBasic.Interaction.'Microsoft.VisualBasic, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
make the RunOnClient property to true.

MyValue := MSDialog.InputBox('Please Enter Data','Title','',50,50);

Message(MyValue);

Fantastic thanks!

Konrad_SEC

Using DotNet variable along with InputBox VB interaction is smart but how to keep the dialog box centered on the screen?
To be able to do so I should leave the last two parameters blank (XPos and YPos). However by doing so I get the following C/AL error message during compiling: "When the funcion is called, the minium numer of parameters should be used. For example:..."

The syntax I am trying to use is: "TextDate := MSDialog.InputBox(Text002,Text003,'YY-MM-DD'); " or "TextDate := MSDialog.InputBox(Text002,Text003,'YY-MM-DD',,);" but none of them works.

I am using NAV 7.0.
Does any have any idea how to overcome this?

ara3n

you can use the screen width and divide it by half

http://msdn.microsoft.com/en-us/library ... width.aspx

FDP

Is there any way to permanently allow this dotNet componnenent, so the user don't get this warning every day:
Microsoft Dynamics NAV

---

The Microsoft Dynamics NAV client needs permission to run Microsoft.VisualBasic.Interaction - an external component. While external components can be useful, they can potentially harm your computer. Only run external components from publishers that you trust. If you do not allow the component to run, then you may not have complete functionality.

Allow for this client session.
Do not allow for this client session.

---

Cancel OK

---