The Update procedure
This update adds Microsoft Office 365 connection objects to the repository. Use it when the installed product supports Office 365 connections but the repository tree does not show the Office 365 connection group. The feature is not hiding. It just has nowhere to sit.
It applies to repositories used by Advanced ETL Processor and Visual Importer ETL.
Before you run the SQL
- Create a repository backup.
- Stop services, schedulers, and designers connected to the repository.
- Run the SQL against the repository database used by the application.
- Restart the application before checking the connection tree.
Run this SQL against the repository
Insert into OBJECT_TYPES
(OBJECT_TYPE,OBJECT_TYPE_NAME,OBJECT_TYPE_GROUP)
Values
(913,'Office 365 Connection',28000)
Insert into OBJECT_TYPES
(OBJECT_TYPE,OBJECT_TYPE_NAME,OBJECT_TYPE_GROUP)
Values
(914,'Office 365 Connections',28000)
INSERT INTO OBJECTS_TREE
(OBJECT_ID,
PARENT_ID,
NAME,
OBJECT_TYPE
)
Select
OBJECT_ID*-7 as OBJECT_ID,
PARENT_ID,
'Office 365' as NAME,
913 as OBJECT_TYPE
From
OBJECTS_TREE
where
OBJECTS_TREE.OBJECT_TYPE=322
UPDATE OBJECT_TYPES
set OBJECT_TYPE_GROUP=28000
WHERE OBJECT_TYPE= '913'
UPDATE OBJECT_TYPES
set OBJECT_TYPE_GROUP=28000
WHERE OBJECT_TYPE= '914' After the repository update
Start the product and open the connection tree. Office 365 should appear with the other connection objects. If it does not, check the repository connection settings first. Nine times out of ten, the SQL was run against the wrong database and the correct one is sitting there looking innocent.