Skip to content

KVSKBAMasterDocReportMgt#

Procedures#

AddMasterDocItemAttribValueMapping(Codeunit KVSKBAMasterDoc, Record KVSKBADocumentHeaderBuffer, Enum KVSKBADocumentTableType, Integer, Code[20], Integer) :#

procedure AddMasterDocItemAttribValueMapping(var MasterDoc: Codeunit "KVSKBAMasterDoc"; var DocumentHeaderBuffer: Record "KVSKBADocumentHeaderBuffer"; DocLineBufferTableType: Enum "KVSKBADocumentTableType"; DocLineNoPar: Integer; ItemNoPar: Code[20]; DocLineIndentation: Integer):

Events#

OnAddMasterDocItemAttribValueMappingOnBeforeSetFilterScopeItemAttribValueMapping(Record Item Attribute Value Mapping, Record KVSKBADocumentHeaderBuffer, Boolean) :#

Summary: Integration event triggered before filtering item attribute value mappings by scope.

[IntegrationEvent(false, false)]
local procedure OnAddMasterDocItemAttribValueMappingOnBeforeSetFilterScopeItemAttribValueMapping(var ItemAttributeValueMapping: Record "Item Attribute Value Mapping"; DocumentHeaderBuffer: Record "KVSKBADocumentHeaderBuffer"; var Handled: Boolean): 

[EventSubscriber(ObjectType::Codeunit, Codeunit::"KVSKBAMasterDocReportMgt", 'OnAddMasterDocItemAttribValueMappingOnBeforeSetFilterScopeItemAttribValueMapping', '', false, false)]
local procedure DoSomethingOnAddMasterDocItemAttribValueMappingOnBeforeSetFilterScopeItemAttribValueMapping(var ItemAttributeValueMapping: Record "Item Attribute Value Mapping"; DocumentHeaderBuffer: Record "KVSKBADocumentHeaderBuffer"; var Handled: Boolean)
begin
end;

Parameters:

  • ItemAttributeValueMapping: The item attribute value mapping record (can be filtered).
  • DocumentHeaderBuffer: The document header context.
  • Handled: Set to true to skip the standard scope filtering logic.

Remarks: Use this event to apply custom filters to the item attribute value mappings. For example, you could filter by additional criteria or exclude certain attribute types. Set Handled to true to completely replace the standard filtering logic. The ItemAttributeValueMapping is already filtered by Table ID and Item No. when this event is raised.

OnAddMasterDocItemAttribValueMappingOnAfterSetPrintAttribut(Record Item Attribute Value Mapping, Record KVSKBADocumentHeaderBuffer, Boolean) :#

Summary: Integration event triggered after determining whether an attribute should be printed.

[IntegrationEvent(false, false)]
local procedure OnAddMasterDocItemAttribValueMappingOnAfterSetPrintAttribut(var ItemAttributeValueMapping: Record "Item Attribute Value Mapping"; KVSKBADocumentHeaderBuffer: Record "KVSKBADocumentHeaderBuffer"; var PrintAttribut: Boolean): 

[EventSubscriber(ObjectType::Codeunit, Codeunit::"KVSKBAMasterDocReportMgt", 'OnAddMasterDocItemAttribValueMappingOnAfterSetPrintAttribut', '', false, false)]
local procedure DoSomethingOnAddMasterDocItemAttribValueMappingOnAfterSetPrintAttribut(var ItemAttributeValueMapping: Record "Item Attribute Value Mapping"; KVSKBADocumentHeaderBuffer: Record "KVSKBADocumentHeaderBuffer"; var PrintAttribut: Boolean)
begin
end;

Parameters:

  • ItemAttributeValueMapping: The item attribute value mapping record being evaluated.
  • KVSKBADocumentHeaderBuffer: The document header context.
  • PrintAttribut: Whether the attribute should be printed (can be modified).

Remarks: Use this event to override or extend the print decision logic for item attributes. The standard logic checks the Print Administration settings based on document scope and type. You can modify PrintAttribut to force an attribute to be printed or excluded. This is useful for implementing custom business rules for attribute visibility.