Chuyển đến nội dung chính

Song Nghia - Technical Consultant

Tìm kiếm Blog này

Từ bài sau sẽ chuyển sang ghi tiếng anh hết

vào tháng 12 08, 2017

Nhận đường liên kết
Facebook
Twitter
Pinterest
Email
Ứng dụng khác

Nhắc nhở tự bài đang sau sẽ chuyển sang tiếng anh, sai thì chịu vậy mới lên cấp được

Nhận đường liên kết
Facebook
Twitter
Pinterest
Email
Ứng dụng khác

Bài đăng phổ biến

Class extension via method wrapping and Chain of Command (CoC)

Class extension via method wrapping and Chain of Command (CoC) Song Nghia - Technical Consultant The functionality for class extension, or class augmentation, has been improved in Microsoft Dynamics 365 for Finance and Operations. You can now wrap logic around methods that are defined in the base class that you're augmenting. You can extend the logic of public and protected methods without having to use event handlers. When you wrap a method, you can also access public and protected methods, and variables of the base class. In this way, you can start transactions and easily manage state variables that are associated with your class. For example, a model contains the following code. Copy class BusinessLogic1 { str DoSomething(int arg) { … } } You can now augment the functionality of the DoSomething method inside an extension class by reusing the same method name. An extension class must belong to a package that references the model where the au

ERROR: Cannot call NEXT, update(), or delete() on buffer

This is a very basic concept. If you get the following error: "Cannot call NEXT, update(), or delete() on buffer where data is selected or inserted in another transactionscope." It means that the record selected has table caching activated, such as ‘NotInTTS’ and that you attempted to, for example run code like the following: //wrong select firstonly forupdate aRecord; ttsbegin; aRecord.delete(); ttscommit; It is important in general and necessary for cached tables to begin the transaction scope before selecting the record for update. And so, even for tables that do not have caching enabled, it is strongly discouraged to call NEXT, update(), or delete() on a buffer outside of the transaction scope it was selected in. //good ttsbegin; select firstonly forupdate aRecord; aRecord.delete(); ttscommit;

AIF WEB SERVICE

1. AIF WEB SERVICE 3 3.1 PREPARATION - Contract class in X++: this class will become one object in .Net - SysEntryPoint class in X++: this class will contain method which developed in X++, and be called outside AX (ex: Website, App,..) - Service and Service Group in X++: this object will publish SysEntryPoint become web service - .Net project to test your service 3.2 DEVELOPMENT Link document: https://drive.google.com/open?id=1cbV-MSPsz5C6HhTduqk1fY7hJ8bQt5jB

Được tạo bởi Blogger