存档

2015年6月 的存档

NAV2015 累计更新-8#

2015年6月30日 评论已被关闭

发布版本号 Build No. – 41370

发布日期 Release Date – June, 2015

下载链接

更新项:
——————————————————————————————————————–

ID Title
372070 The DotNet variable property, SuppressDispose, is not supported by the Application Merge Utilities powershell commands.
371810 The page freezes when the user does not have permission to open the action.
371924 “Paste failed because of validation errors.” error when you try to copy and paste rows on the Allocations page of the Recurring General Journal page.
372171 The user’s From address is not populated when you send an e-mail confirmation of a sales order.
371795 Hiding a column in the Windows client with the IdentationControls and IdentationColumnName set does not work.
371686 The pointer always stays on the first field when a page is opened.
372204 The ADCS – Cursor position is wrong on the terminal when double-byte character sets are used.
372157 Error is not catched in Codeunit OnRun when the Buffered Insert setting is active.
372228 Updates to support Microsoft Social Engagement.
373107 The Web client stops responding in Safari after iOS is updated to the 8.x version.
372073 AMU cmdlets fail if the development environment is set to a language other than ENU.
371921 You cannot select a lookup field in a FactBox.
372290 XMLPort crashes the client.
371646 Mouse pointer for cues, links, and drilldowns in the Windows client does not change when the Windows pointer for Link Select is changed in Windows and it is always a “hand.”
372300 Local variables are missing after merge.
374748 NAV Server installer has a dependency to .Net 3.0 or 3.5.
372320 The MultiLine property does not work in non-editable fields in the Web client.
372250 Notes cannot be added to the Sales Prices, Sales Line Discount, Purchase Prices, and Purchase Line Discounts pages.
372028 The Page.Run function does not accept the Field parameter.
372053 Table relations with filters show an error in some circumstances.
分类: Uncategorized 标签:

NAV2013R2 累计更新-20#

2015年6月30日 评论已被关闭

发布版本号 Build No. – 41371

发布日期 Release Date – June, 2015

下载链接

更新项:
——————————————————————————————————————–

ID Title
372054 The ADCS – Cursor position is wrong on the terminal when double-byte character sets are used.
372147 Error is not catched in Codeunit OnRun when the Buffered Insert setting is active.
371852 XMLPort crashes the client.
371614 Mouse pointer for cues, links, and drilldowns in the Windows client does not change when the Windows pointer for Link Select is changed in Windows and it is always a “hand.”
373099 The Web client stops responding in Safari after iOS is updated to the 8.x version.
363531 The upgrade process deletes all database logins.
364609 The G/L Total-Balance report does not show the name of some accounts if you save it as a PDF, Word, or Excel file in the German version.
372061 Error when you rename a Windows user.
374727 Data is changed after you run the Export to Excel function.
分类: Uncategorized 标签:

NAV2013 累计更新-27#

2015年6月30日 评论已被关闭

发布版本号 Build No. – 41354

发布日期 Release Date – June, 2015

下载链接

更新项:
——————————————————————————————————————–

ID Title
371866 “Compilation of CodeUnit xxx failed because of an I/O error on the following computer” error message when you try to run a job queue process.
372188 The Web client stops responding in Safari after iOS is updated to the 8.x version.
分类: Uncategorized 标签:

销售至与发票至的区别

2015年6月22日 评论已被关闭

在NAV中, 我们知道销售订单头上有两个信息. 分别是Sell-to 和 Bill-to, 销售至和发票至客户编号. 通常这两个信息是一致的. 那么这两个信息的设置目的是什么呢?

通常, 针对集团型客户, 可能客户有多个独立下属公司, 但资金结算却仅与集团下属的资金公司产生业务往来. 这样的客户就会存在销售至和发票至分别设置信息.

那么NAV在实际业务上, 到底是用哪个数据呢, 下面按照业务进行逐一介绍.

1. Order Dimension 订单维和订单行维

我们来看看Bill-To Customer No.的OnValidate代码.

CreateDim(
DATABASE::Customer,”Bill-to Customer No.“,
DATABASE::”Salesperson/Purchaser”,”Salesperson Code”,
DATABASE::Campaign,”Campaign No.”,
DATABASE::”Responsibility Center”,”Responsibility Center”,
DATABASE::”Customer Template”,”Bill-to Customer Template Code”);

从代码上看到, 是从”Bill-to Customer No.”来取得默认维.

2. 价格与折扣

打开Codeunit 7000 , 其中关于价格和折扣的获取来源. 也是采用Bill-to Customer No.

WITH SalesLine DO
IF (Type = Type::Item) AND Item.GET(“No.”) THEN BEGIN
FindSalesPrice(
TempSalesPrice,”Bill-to Customer No.“,SalesHeader.”Bill-to Contact No.”,
“Customer Price Group”,”,”No.”,”Variant Code”,”Unit of Measure Code”,
SalesHeader.”Currency Code”,SalesHeaderStartDate(SalesHeader,DateCaption),ShowAll);
EXIT(TempSalesPrice.FINDFIRST);
END;

 
WITH SalesLine DO
IF (Type = Type::Item) AND Item.GET(“No.”) THEN BEGIN
FindSalesLineDisc(
TempSalesLineDisc,”Bill-to Customer No.“,SalesHeader.”Bill-to Contact No.”,
“Customer Disc. Group”,”,”No.”,Item.”Item Disc. Group”,”Variant Code”,”Unit of Measure Code”,
SalesHeader.”Currency Code”,SalesHeaderStartDate(SalesHeader,DateCaption),ShowAll);
EXIT(TempSalesLineDisc.FINDFIRST);
END;
EXIT(FALSE);

 

3. 分类帐分录(Item Ledger Entry和Value Entry)

打开Codeunit 80, 其中关于ItemJnlLine.Source No.指定的来源, 我们看到这里指向的是Sell-to Customer No.
ItemJnlLine.”Source Type” := ItemJnlLine.”Source Type”::Customer;
ItemJnlLine.”Source No.” := “Sell-to Customer No.“;

那么相应的物料分析报告(主要指销售模块下的按客户/按物料分析销量,销售额等), 是以Sell-to Customer No.进行相关分析.

 

4. 总帐分录, 客户分类帐分录(G/L Entry和Cust. Ledger Entry)

我们还是打开Codeunit 80, 其中关于GenJnlLine.”Source No.”指定的来源, 我们看到这里指向的是Bill-to Customer No.
GenJnlLine.”Source Type” := GenJnlLine.”Source Type”::Customer;
GenJnlLine.”Source No.” := “Bill-to Customer No.“;
GenJnlLine.”Posting No. Series” := “Posting No. Series”;

那么相应的总帐相关分析报告, 帐龄分析等都是以Bill-to Customer No.进行相关分析.

 

分类: Uncategorized 标签:

NAV2015之自动填写变量名称

2015年6月12日 评论已被关闭

在NAV2015中, 新增了一个小功能, 在我们定义变量时, 不需要指定其名称, 系统会自动生成相应的变量名.

如下图所示:

定义一个Prod. Order Component表的变量. Name处留空.

到下一行后, 系统将自动生成变量名ProdOrderComponent.

如果再下方继续创建Prod. Order Component表变量, 并在Name处留空, 系统会自动生成ProdOrderComponent2.

 

系统自动为我们生成的变量名还是非常容易识别的. 当然我们也需要了解一些系统变量常见命名规则. 如:

变量名
ItemLedgEntry Item Ledger Entry
GLEntry G/L Entry
ValueEntry Value Entry
ItemJnlLine Item Journal Line
GenJnlLine Gen. Journal Line
分类: Uncategorized 标签: