Command Button Creation

Skolnick

I am creating two command buttons. The first button will be a Print Preview button and the second button will be a Print Sales Quote (or Order depending on the application at the time) button.

Through Object Designer, the command buttons have been created and the PushAction is set to RunObject. From this point, how do I find out which action is the preview action and which one is the Print action?

Is this the correct way to create these buttons?

Thanks for the info!

girish.joshi

Instead of setting the runobject, call the object you want to run in the onpush trigger of the command button. simply remove the run object, and f9 on the button and you will get to this trigger.

Before you call the the object, set a global variable in the codeunit or the report to let it know whether or not you will be printpreviewing.

You set the globalvariable through a setter function in your report.

Skolnick

I don't have a Developer's License. Is the only way to complete this task is for me to design the form and then have my partner finish the code?

I know there's just a couple lines of code that need to be added (as was shown to me at Convergence) but hoped that with my license, I could design the buttons and enable the tasks with the granules owned.

Any thoughts?

Oh, and thank you for the very quick reply. I appreciate it!

ara3n

skolnick, yes you need to do it through code. do most of the work yourself and ask the parter to add the code.
Did they show Navision 5? I heard Bill Gates will demo it.

Skolnick

Thanks for the info.

Yes, BG did show the software and "Dynamics NAV" showed the new iteration as well. The look and feel is different but once users get used to it, it should be fine.

As for Application Designer, I think MS wants everyone to migrate to SQL and use the report designer in that software instead. We are still on C-Side and have not upgraded to SQL.

I had the opportunity to speak there on Future Value of Current Version and really enjoyed it. Would not mind speaking again at a future conference as a user. The audience got a lot out of the subject, too.

Thx!