1 of 29 Microsoft ® Business Solutions–Navision ® Development I – C/SIDE Introduction – Day...
-
Upload
gervais-scott -
Category
Documents
-
view
213 -
download
0
Transcript of 1 of 29 Microsoft ® Business Solutions–Navision ® Development I – C/SIDE Introduction – Day...
1 of 29
Microsoft ® Business Solutions–Navision®Microsoft ® Business Solutions–Navision®
Development I – C/SIDE Introduction – Day 1
2 of 29
IntroductionsIntroductions
Name
Company
Job role
Experience with product
Favorite hobby/activity
3 of 29
Things you need to knowThings you need to know
• Class Information– Starting time– Ending time– Breaks– Lunch
• Facilities– Restrooms– Telephones
4 of 29
Class ScheduleClass Schedule
Monday Tuesday Wednesday Thursday Friday
8:00 Course Introduction (1 hr)
Review (1 hr) Review (1 hr) Review (1 hr) Review (1 hr)
9:00 Introduction to Navision Development (1 hr)
Data Manipulation - MenuSuites (1 hrs)
10:00
11:00 Data Manipulation - Dataports (1 hr)
12:00 Lunch Break Lunch Break Lunch Break Lunch Break Lunch Break
13:00 Architecture - Basic Tables II (1 hrs)
14:00
15:00
16:00
Review Questions (3 hrs)
Data Manipulation - Reports II (2 hrs)
Data Manipulation - XMLports (2 hrs)
Class Review
Data Manipulation - Codeunits (2 hrs)
Integration - Intro & NODBC (2 hrs)
Integration - Automation Server (2 hrs)
Integration OCX (2 hrs)
Architecture - Basic Tables I (2 hrs)
Architecture - Basic Forms I (3 hrs)
C/AL Programming I (3 hrs)
C/AL Programming II (2 hrs)
Data Manipulation - Reports I (2 hrs)
5 of 29
Course Structure – Day 1Course Structure – Day 1
• Course Introduction• Introduction to Microsoft Navision
Development• Basic Design Architecture• The C/AL Programming Language• Ata Manipulation• Integration • Review
6 of 29
IntroductionIntroduction
•Course Content– C/SIDE Overview– Basic Architecture– C/AL Programming Language– Data Manipulation– Integration– Class Review
7 of 29
IntroductionIntroduction
•C/SIDE Fundamentals– C/SIDE User Interface– 7 Application Objects– Physical vs. Logical Database– Logical Database Structure– Integration with External Objects
8 of 29
IntroductionIntroduction
•Further Information– C/SIDE online Help (C/SIDE Reference Guide)– Application Designer’s Guide
9 of 29
TablesTables
Properties Properties
Triggers Triggers
Properties Properties
Properties Properties
Triggers Triggers
Fields Fields
Global Var. Global Var.
Properties Properties
SumIndexFieldsSumIndexFields
KeysKeys
Table Description
10 of 29
Tables – Common Data TypesTables – Common Data Types
Description Size SQL Considerations
Option refers to “Option String” property
4 INTEGER
Integer -2,147,483,647 to 2,147,483,647
4 INTEGER
Decimal 18 significant digits
12 DECIMAL
Date January 1, 0 to December 31, 9999
4 DATETIME8 bytesCannot be before 01/01/1754
Boolean TRUE or FALSE 4 TINYINT1 byte
BigInteger
64 bit integer 8 BIGINT
11 of 29
Tables – Common Data TypesTables – Common Data Types
Description Size SQL Considerations
Text Alphanumeric string up to 250 characters
Max Length + 1byte
VARCHAR1 byte per character
Code Uppercase alphanumeric string up to 250 characters
Max Length + 2 bytes
VARCHAR1 byte per character
BLOB Used to store bitmaps and memos
8 bytes + size IMAGE
12 of 29
Tables – Other Data TypesTables – Other Data Types
• Time• Binary• Dateformula• DateTime• TableFilter• Duration• GUID• RecordID
13 of 29
Tables – KeysTables – Keys
• Primary Key– Unique for each table– Can be composed of up to 20 fields– Always active
• Secondary Key– Optional keys used for sorting– Fields in the secondary key plus the primary
key cannot exceed 20 fields– Can be changed as an inactive key
14 of 29
SIFTSIFT
• SumIndexFields• FlowFields • FlowFilter Fields
15 of 29
SIFTSIFT
FlowField Calculation
Item No. Posting Date Quantity Sum
70000 01.01.01 100 100
70001 01.01.01 10 110
70001 01.10.01 50 160
70001 01.25.01 -5 155
70001 02.01.01 20 175
70002 01.01.01 50 225
Item Ledger Entries Key : Item No., Posting DateSumIndexField : Quantity
Item ‘70001’, InventoryDateFilter: ‘01.01.01..01.31.01’
55 75
155 – 100 = 55
175 – 100 = 75
16 of 29
FlowFieldsFlowFields
• Sum• Average• Exist• Count• Min• Max• Lookup
17 of 29
Tables - TypesTables - Types
Type Brief Description Examples
Master Contains information about the primary focus subject of its functional area.
Customer, Vendor, Item
Supplemental Stores information about a supplemental subject used in one or more functional areas.
Currency
Setup Stores one record that holds general information about its functional area.
G/L Setup, Sales &Receivables Setup
Register A “table of contents” for its corresponding Ledger table or tables.
G/L Register, Item Register
Subsidiary Contains information which is subsidiary to either a Master table or a Supplemental table or both.
Item Vendor, FA Depreciation Book
Ledger Contains the transactional information that is the primary focus of its functional area.
Cust. Ledger Entry, Item Ledger Entry
Journal The primary transaction entry table for a functional area.
Purchase Journal, Item Journal
Document Secondary transactional tables that allow entries in a functional area or into multiple functional areas at once. This is implemented as a pair table.
Sales Header / Sales Line
Document History
Contains the transaction history for documents that have been posted.
Sales Invoice Header / Sales Invoice
18 of 29
Forms – Form TriggersForms – Form Triggers
Properties Properties
Triggers Triggers
Properties Properties
Properties Properties
Triggers Triggers
Controls Controls
Global Var. Global Var.
Form Description
19 of 29
Forms - Five Basic Types of WindowsForms - Five Basic Types of Windows
• Dialogs– Display Information – Usually involves pressing
a button
• Request Panels– Used Primarily to filter Report information.
• Unbound Forms– Forms that are not associated with a Table.
• One-Record Forms– Allows the user to view and possibly edit one
record at a time (Card forms)
• Multi-Record Forms– Include Tabular Forms, TrendScapes, Matrix
Forms
20 of 29
Building Blocks of Microsoft Navision?Building Blocks of Microsoft Navision?
Forms Associated with Tables• One-Record Forms• Multi-Record Forms
These can be broken out into the following…
21 of 29
Form TypesForm Types
• Card Form• Statistics Form• Tabular Form• List Form• Worksheet• Header/Line Form• Setup Form
22 of 29
Card FormCard Form
• Definition: A Card Form allows the user to view and edit one record at a time (in a table).
• Naming: Generally you take the table name and add the word “Card” to the end.
• Example: Item Card
23 of 29
Statistics Form Statistics Form
• Definition: A one-record form that lets the user view, but not edit, information. These usually include FlowFields.
• Naming: Generally you take the table name and add the word “Statistics” to the end.
• Example: Item Statistics
24 of 29
Tabular Form Tabular Form
• Definition: A multi-record form that lets the user view and edit information. These are generally used for initial data entry of Supplemental Table information.
• Naming: Generally you take the table name and adds an ‘s’ to the end.
• Example: Departments
25 of 29
List Form List Form
• Definition: A multi-record form that lets the user view and usually “select” a single record from a list.
• Naming: Generally you take the table name and add the word “List” to the end.
• Example: Item List
26 of 29
WorkSheet Form WorkSheet Form
• Definition: A specialized Tabular form, this multi-record form allows the user view and edit information.
• Naming: Associated with the function and purpose of the table. If entering journal entries, the form would end with “Journal”.
• Example: Cash Receipts Journal
27 of 29
Header/Line Form Header/Line Form
• Definition: A form that contains both a card form and a tabular form.
• Naming: Generally these forms represent a document.
• Example: Sales Order
28 of 29
Setup Form Setup Form
• Definition: A one-record form that allows the user to view and edit the single record in a setup table.
• Naming: Named for the table (or functional area) they represent, adding the word “Setup”.
• Example: Sales & Receivables Setup
29 of 29
Menu Form Menu Form
• Definition: With the release of Microsoft Navision 4.0 and the introduction of the Navigation Pane, Menu Forms are no longer used. You may, however, run into them when working with previous versions.
• Naming: Generally you take the Functional Area of the menu and add the word “Menu” to the end.
• Example: General Ledger Menu