Skip to Content
author's profile photo
Former Member

Access to UDO via DI


we wanted to know if there's a possibility to gain access to a user defined object (UDO) via the DI Api. We wondered if there might be a way to handle UDOs similar to BO system objects, that is to say by requesting a reference using the 'GetBusinessObject' method in order to manipulate them within the source code.

As far as we know yet, the only possibility to perform changes on a UDO is by using the form user interface.



Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    author's profile photo
    Former Member
    Posted on Dec 16, 2004 at 12:40 PM

    Have a look at the UserObjectsMD, it should provide the functionality you're expecting.

    From DI help file:

    UserObjectsMD is a non-business object that represents the registration data settings, such as table name and supported services, of a user defined object.

    This object enables you to:

    Add a user define object.

    Retrieve a user define object by its key.

    Update a user define object .

    Remove a user define object from the database

    Save the object in XML format.

    Source table: OUDO.

    Florian Zeller

    Add comment
    10|10000 characters needed characters exceeded

    • Right.

      Data migration from existing UDTs to UDO-UDTs can at this point in time only happen via SAP Business One UI:

      Note that DBDataSource is much more powerful now!!!!! =>

      You can add complete lines/rows (not in SAP B1 system forms ...) and afterwards add the data to the database - without using DI API...

      I.e. you could create open form, retrieve data from existing UDTs via one DBDataSource and add the data to the DBDataSource for the new UDO UDT + then click the "Add" button on your form (must be in Add mode then, of course). That should do the trick!!!!

      I didn't try exactly this - just worked with UDO, but this is the way it should work; maybe there are preconditions to have the particular DBDataSource fields bound to UI items, but I would expect this not to be necessary...