Changes in C/AL Behavior and Support from Earlier Versions of Microsoft Dynamics NAV

  • [アーティクル]

The following table provides an overview of the new, removed, or changed C/AL data types, functions, properties, and triggers in Microsoft Dynamics NAV 2013 since the previous version of Microsoft Dynamics NAV. For more information about the changes, see the specific topic about the data type, function, property, or trigger.

Data type, function, property, or trigger Change

AutoReplace Property

Applies to XMLports.

AutoSave Property

Applies to XMLports.

AutoUpdate Property

Applies to XMLports.

BEEP Function

Not supported on Microsoft Dynamics NAV Server.

Binary Data Type

The Binary data type, used in earlier versions of Microsoft Dynamics NAV to store fixed lengths of binary data in a record, is not supported in Microsoft Dynamics NAV 2013. If you previously used the BINARY data type, consider using the BLOB Data Type instead.

BLOB Data Type

If you call the CALCFIELDS Function (Record) on a BLOB field, then you get the value of the BLOB that is in the database, not the value that you wrote to a BLOB OutStream.

BottomMargin Property

Not supported in Microsoft Dynamics NAV 2013 reports.

CALCFIELDS Function (Record)

CALCFIELDS execution is decoupled from Microsoft Dynamics NAV SIFT index definitions. This can reduce the number of required SIFT indices, which can improve performance.

CALCSUM Function (FieldRef)

CALSUM execution is decoupled from Microsoft Dynamics NAV SIFT index definitions. This can reduce the number of required SIFT indices, which can improve performance.

CALCSUMS Function (Record)

CALSUMS execution is decoupled from Microsoft Dynamics NAV SIFT index definitions. This can reduce the number of required SIFT indices, which can improve performance.

CardFormID Property

Name changed to CardPageID Property.

Code Data Type

The Code data type supports Unicode in Microsoft Dynamics NAV 2013.

Microsoft Dynamics NAV 2013 does not enforce a limit on the length of a Code variable. You can specify a maximum length in the C/AL Globals or C/AL Locals window when you create the variable, but it is not required.

COMMANDLINE Function

Not supported in Microsoft Dynamics NAV 2013.

COUNT Function (Record)

In Microsoft Dynamics NAV 2013, the COUNT function does not always ignore security filters. It adheres to the SecurityFiltering Property.

COUNT Function (RecordRef)

In Microsoft Dynamics NAV 2013, the COUNT function does not always ignore security filters. It adheres to the SecurityFiltering Property.

COUNTAPPROX Function

Not supported in Microsoft Dynamics NAV 2013.

CREATETOTALS Function

Redundant in Microsoft Dynamics NAV 2013 reports. We recommend that you use the SUM function in Visual Studio instead.

Dataports

Not supported in Microsoft Dynamics NAV 2013. Use XMLports instead.

Debugger functions

New functions.

DELETE Function (Record) and DELETE Function (RecordRef)

You cannot call the DELETE function on a record for table 2000000001, the Object table or table 2000000006, the Company table.

DrillDownFormID Property

Name changed to DrillDownPageID Property.

ENVIRON Function

Not supported in Microsoft Dynamics NAV 2013.

EXPORT Function (BLOB)

Not supported in Microsoft Dynamics NAV 2013.

EXPORTOBJECTS Function

Not supported in Microsoft Dynamics NAV 2013. Use the finsql.exe executable with the ExportObjects command instead. For more information, see ExportObjects.

Forms

Not supported in Microsoft Dynamics NAV 2013.

FormHandler Function

Name changed to PageHandler.

IMPORT Function (BLOB)

Not supported in Microsoft Dynamics NAV 2013.

IMPORTOBJECTS Function

Not supported in Microsoft Dynamics NAV 2013. Use the finsql.exe executable with the ImportObjects command instead. For more information, see ImportObjects.

INSERT Function (Record) and INSERT Function (RecordRef)

You cannot call the INSERT function on a record for table 2000000001, the Object table or table 2000000006, the Company table.

ISSERVICETIER Function

Obsolete in Microsoft Dynamics NAV 2013, but still supported. This function always returns true.

LANGUAGE function

Not supported in Microsoft Dynamics NAV 2013.

LookupFormID Property

Name changed to LookupPageID Property.

ModalFormHandler Function

Name changed to ModalPageHandler.

MODIFY Function (Record) and MODIFY Function (RecordRef)

Microsoft Dynamics NAV 2013 does not let you modify the database by using an old copy of a record.

You cannot call the MODIFY function on a record for table 2000000001, the Object table or table 2000000006, the Company table.

NEWPAGE Function

Not supported in Microsoft Dynamics NAV 2013 reports.

NEWPAGEPERRECORD Function

Not supported in Microsoft Dynamics NAV 2013 reports.

OBJECTID Function

Not supported in Microsoft Dynamics NAV 2013 reports.

OnAfterModifyRecord Trigger

New XMLport trigger.

OnBeforeModifyRecord Trigger

New XMLport trigger.

OnCreateHyperlink Trigger

Not supported in Microsoft Dynamics NAV 2013 reports.

OnHyperlink Trigger

Not supported in Microsoft Dynamics NAV 2013 reports.

OnPreSection Trigger

Not supported in Microsoft Dynamics NAV 2013 reports.

OnPostSection Trigger

Not supported in Microsoft Dynamics NAV 2013 reports.

OSVERSION Function

Not supported in Microsoft Dynamics NAV 2013.

PAGENO Function

Not supported in Microsoft Dynamics NAV 2013 reports.

PAPERSOURCE Function

Not supported in Microsoft Dynamics NAV 2013 reports.

PaperSourceDefaultPage Property

New report property.

PaperSourceFirstPage Property

New report property.

PaperSourceLastPage Property

New report property.

PaperSourceOtherPages Property

Not supported on Microsoft Dynamics NAV 2013 reports.

Query object

New object.

RECORDLEVELLOCKING Function (Record and RecordRef)

Not used in Microsoft Dynamics NAV 2013. The function is still available and compiles but always returns true.

READCONSISTENCY Function (Record and RecordRef)

Not used in Microsoft Dynamics NAV 2013. The function is still available and compiles but because Microsoft Dynamics NAV 2013 uses SQL Server's locking mechanisms and does not use snapshots like earlier versions of Microsoft Dynamics NAV, the return value is always false.

Rename function

Microsoft Dynamics NAV 2013 does not let you modify the database by using an old copy of a record.

RequestOptionsForm system variable

Not supported in Microsoft Dynamics NAV 2013.

RunFormLink Property

Name changed to RunPageLink Property.

RunFormOnRec Property

Name changed to RunPageOnRec Property.

RunFormView Property

Name changed to RunPageView Property.

SAVEASHTML Function

Not supported in Microsoft Dynamics NAV 2013 reports.

SAVEASXML

Not supported in Microsoft Dynamics NAV 2013 reports.

SETAUTOCALCFIELDS Function (Record)

New function to calculate FlowFields at the same time that you retrieve them from the database.

SETCURRENTKEY Function (Record)

In Microsoft Dynamics NAV 2013, you do not have to define keys only for SIFT indexes. Fewer SIFT indices and fewer Microsoft Dynamics NAV keys can improve performance.

SETPERMISSIONFILTER Function (Record)

Not supported in Microsoft Dynamics NAV 2013. Instead, you change the SecurityFiltering Property from Validated to Filtered.

SETPERMISSIONFILTER Function (RecordRef)

Not supported in Microsoft Dynamics NAV 2013. Instead, you change the SecurityFiltering Property from Validated to Filtered.

SaveTableView property

Not supported in Microsoft Dynamics NAV 2013.

SHELL Function

Not supported in Microsoft Dynamics NAV 2013.

SHOWOUTPUT Function

Not supported in Microsoft Dynamics NAV 2013 reports.

Sessions

New functions.

SubFormLink Property

Name changed to SubPageLink Property.

SubFormView Property

Name changed to SubPageView Property.

SYNCHRONIZEALLLOGINS Function

Not supported in Microsoft Dynamics NAV 2013.

SYNCHRONIZESINGLELOGIN Function

Not supported in Microsoft Dynamics NAV 2013

Test Pages

New objects and functions.

Text Data Type

The Text data type supports Unicode in Microsoft Dynamics NAV 2013.

Microsoft Dynamics NAV 2013 does not enforce a limit on the length of a Text variable. You can specify a maximum length in the C/AL Globals or C/AL Locals window when you create the variable, but it is not required.

TOTALSCAUSEDBY Function

Not supported in Microsoft Dynamics NAV 2013 reports.

TransactionType Property

In Microsoft Dynamics NAV 2013, the default transaction isolation level is REPEATABLE READ. In earlier versions of Microsoft Dynamics NAV, it was SERIALIZABLE. This affects FIND and NEXT function calls when transaction type is Update, Snapshot, or UpdateNoLocks.

URL Function

Not supported on Microsoft Dynamics NAV 2013 reports.

UseReqForm Property

Name changed to UseRequestPage Property.

VARIABLEACTIVE Function

Not supported in Microsoft Dynamics NAV 2013.

VISIBLE Function

Not supported in Microsoft Dynamics NAV 2013.

YIELD Function

Not supported on Microsoft Dynamics NAV Server.

See Also

Concepts

Functions Not Supported by Microsoft Dynamics NAV Web Client and Microsoft Dynamics NAV Portal Framework
Page Properties Not Supported by Microsoft Dynamics NAV Web Client and Microsoft Dynamics NAV Portal Framework