Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 302 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Table 'TempBlob' is marked for removal. Reason: Replaced by BLOB Storage Module
tomasevicstefan
Member Posts: 51
Hi all,
How shall we call Codeunit.Run(CodeunitID, TempBlob) if TempBlob will be removed in future?
Thanks
How shall we call Codeunit.Run(CodeunitID, TempBlob) if TempBlob will be removed in future?
Thanks
0
Best Answer
-
Wisa123
Member Posts: 308
Hi,
Since TempBlob is'nt a table anymore the current Codeunit.Run will not work in the future.
"Workaround": Create a procedure and just pass the TempBlob Codeunit or Streams.
However this is not really a generic approach and won't work in scenarios where the Codeunit ID is somehow determined by your business logic.
As long as it's supported there's nothing wrong with using Codeunit.Run with the TempBlob table.
Since (as announced at Techdays) interfaces are going to be a thing in Business Central, maybe we get possibility to pass in an interface implementation into a Codeunit (-> Dependency Injection). However I wouldn't count on that.
So either refactor your solution to get rid of the Codeunit.Run calls with the Tempblob, or wait and hope for MS to give us something handy to deal with this scenario.
/Wisa
Austrian NAV/BC Dev5
Answers
Since TempBlob is'nt a table anymore the current Codeunit.Run will not work in the future.
"Workaround": Create a procedure and just pass the TempBlob Codeunit or Streams.
However this is not really a generic approach and won't work in scenarios where the Codeunit ID is somehow determined by your business logic.
As long as it's supported there's nothing wrong with using Codeunit.Run with the TempBlob table.
Since (as announced at Techdays) interfaces are going to be a thing in Business Central, maybe we get possibility to pass in an interface implementation into a Codeunit (-> Dependency Injection). However I wouldn't count on that.
So either refactor your solution to get rid of the Codeunit.Run calls with the Tempblob, or wait and hope for MS to give us something handy to deal with this scenario.
/Wisa