Wednesday, July 29, 2009

C/SIDE Concepts

Description of C/SIDE Concepts

Properties control the appearance and behavior of the application objects and all their sub-objects. Properties are used to control the appearance of data, specify default values, specify colors, and define relationships.

C/AL is the language you use to write functions in C/SIDE. In the previous table, "C/AL" refers to functions written in this language.

A trigger is a mechanism that is built into an application object. When certain actions are performed on the application object, the trigger initiates an action. You can add your own C/AL code to the trigger to modify the default behavior of the application object or extend its functionality.

Keys define the order in which data is stored in your tables. You can speed up searches in tables by defining several keys which sort information in different ways.

A field is the smallest building block in your database. A field typically stores information such as a name or a number.

Controls are objects on a form or report that display data, perform actions, or enhance the appearance of the form, such as command buttons and text labels.

Request Form
A request form is a form that is used in a report. Before a report is run, a request form is displayed to let the user specify filters and options for the report.

A template defines the overall layout of a report.

Data Items
A data item is a building block for defining a model of your data when you create a report. You use a hierarchy of data items to define which data the report will contain. A data item represents a table, and when you run a report, the system cycles through the records in the associated table. A data item can have one or more sections.

A section is a substructure of a data item, where you place controls to display information. You will typically use sections that define the body, header, and footer in your report.

Object-Oriented vs. Object-Based

C/SIDE is not object-oriented but object-based. This is an important distinction. In an object-oriented language or environment, a developer can create new types of objects based on the ones already in the system. In Microsoft Dynamics NAV, you can only create objects that are either tables, forms, pages, reports, dataports, XMLports, codeunits, or menu suite objects.Because there are a limited number of application objects, C/SIDE works faster and more efficiently. The greatest benefit is the Stability.

Object Designer

The Object Designer is the main tool for developing C/SIDE applications. This tool allows you to do the following:
. Design new tables, forms, pages, reports, dataports, XMLports, menusuites and codeunits.
. View existing application objects.
. Modify existing application objects.
. Run an application object (with the exception of XMLports, menusuite objects and pages).

Tools in the Object Designer
The following table lists the tools that are available in the Object Designer.

Tool - Designed for

Table Designer - Tables
Form Designer - Forms
Page Designer - Pages
Report Designer - Reports
Dataport Designer - Dataports
XMLport Designer - XMLports
C/AL editor - Codeunits
Navigation Pane Designer - MenuSuite objects

Monday, July 27, 2009

C/SIDE Fundamentals

Here I am giving an Introduction to user interface and to some of the basic concepts that are relevant to application design such as the different object types.
C/SIDE applications are based on certain application objects. They are
You use tables to store data. For example, a business application usually contains a customer table that stores information about each customer.Understanding tables is the key to using all the other objects.
You use forms to access the information that is stored in the tables. You use forms when you enter new information and when you view information that already exists in the database.
You use reports to present information. You use filters and sorting to select the data that you want to present in a report.
You use dataports to import data from and export data to external text files.
A codeunit contains user-defined functions written in C/AL code. C/AL is the application language you use to write functions in C/SIDE. The functions that a codeunit contains can be used from the other objects in your application. This helps to minimize application size because the same code can be reused.
A MenuSuite object contains the set of menus that are displayed in the Navigation Pane.
Pages have the same functionality as forms but are intended to run on the RoleTailored client. A page can be role tailored, to suite a users needs.

Zoom Funtion In Navision

In the Classic client, you use the Zoom feature on a form to view all fields for the current record that are in the table on which the form is based. For example, if you open a sales order form, click the Tools menu, and then click Zoom, then the Sales Header - Zoom window opens. The Sales Header - Zoom window shows all fields in the Sales Header table and the value of each field for the current record.
You can use the Zoom feature in the Classic client to help you troubleshoot and debug issues. For example, if you create a new form and need to troubleshoot the data that is displayed on the form, then you can use the Zoom feature to view all fields for the current record.