Hello,
is it allowed to save data to a user defined table via a stored procedure using the DI-RecordSet or does this count as a kind of external modification?
Extending the possibilities: Is it allowed to generate a View in the database which accesses user defined tables? We know that CREATE/ALTER/DROP is forbidden by the DI-API and not allowed to be executed on UDTs, but what about Views using UDTs?
The reason for this question is easy: We want to relocate SQL/UserTable-code with JOINs from within our program into the database if possible. Stored procedures would mean a tremendous relief in accessing user defined tables but only if both ways, loading data via stored procedure into the recordset and saving back its tuples via another stored procedure are allowed.
Views would easing this only more, as we could define a view on the joined UDT and saving could be done automatically.
Ch. Becker
1 Answer
-
Best AnswerPosted on Feb 07, 2005 at 02:26 PM
Hello,
When using classical UDTs, there are no internal fields that are filled from SAP Business One - or DI API.
Therefore using a view on the joint table to write data into the UDTs will NOT count as "external modification".
You can feel free to use SQL statements that modify data, Views, stored procedures; nevertheless - as you mentioned - you are not allowed to change field definitions - or keys except through DI API meta data objects!
HTH,
Frank
PS: Please note that there are a lot of internal fields in UDTs used for UDOs. In this case you should better wait until DI API exposes UDOs (data! UDO meta data are already supported)! That should happen in the course of the next releases.
Add a comment
Add a comment