-
Notifications
You must be signed in to change notification settings - Fork 631
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Event Request] Remove DotNet parameters from events #15140
Comments
Normally you can only add the need parameters to a event subscriber. Without the Dotnet parameters a event subscriber should be possible. [IntegrationEvent(false, false)]
local procedure OnFillPackageMetadataFromXMLOnAfterGetPackageTableValueFromXML(ConfigPackageTable: Record "Config. Package Table"; var TableNode: DotNet XmlNode)
begin
end; [EventSubscriber(ObjectType::Codeunit, Codeunit::"Config. XML Exchange", 'OnFillPackageMetadataFromXMLOnAfterGetPackageTableValueFromXML', '', false, false)]
local procedure OnFillPackageMetadataFromXMLOnAfterGetPackageTableValueFromXML(ConfigPackageTable: Record "Config. Package Table")
begin
end;
} Wouldn't it be better if the Codeunit is refactored to the new XMl Types with new events.... |
Sure, I know that you can leave the parameters you don't need. But in this case, I need the Xml parameter. Obviously, the best way to get rid of the DotNet parameters is to refactor the codeunit. I guess Microsoft is smart enough to recognize that. 😊 But after all, I don't really care what variable types are used internally, as long as I can use the events. 😊 |
Hi, Do you have any suggestions which parameters should be used instead of DotNet to fit you needs (same object as text, etc)? |
It is used to create extra XML elements and add them to the TableNode parameter. In this case a feature that is similar to "Dimensions as Columns", but for item specifications. For example:
|
Can you please remove the DotNet variables from the events in codeunit 8614 "Config. XML Exchange"
Some events in this codeunit pass parameters as DotNet objects. So they can't be used in a cloud extension.
Internal work item: AB#416596
The text was updated successfully, but these errors were encountered: