Sage 100

Sage Intelligence Import of report with additional Connections. Issue is that when the import is completed without any errors the report doesn't work. The report doesn't work because the System DSN connection I have referenced doesn't exist. I thought the export process exports the connection as well as the containers within it. Am I missing something here? I know the system dsn that is being referenced by the container needs to exist and it does but the connection and the containers are not created. Which means I will have to manually recreate it. Which will also mean that the customer will need to have a connector license. (tried to import with and without connector license but no change)

Todd - when Intelligence first was released, if you try the bulk import the connections would be created, however I think they were going to ""fix"" that so if you create a report using a different connector, then the client needs to purchase the connector module.

That would be different than what I have been told by Sage about requiring the connector. I have always been told that the customer doesn't need connector, if you create the reports, since the container is created when imported. They would only need it if they needed to create a new container. I tried it with a key that has connector and it still didn't import in. So something else is going on. I am going to check to make sure that the reports are referencing the correct container.

It would interesting to hear what they say to you. We were told that if you create a report which uses the auto connect connector then you don't need a connector license. However if you add other fields or tables to the connection you are using then the customer needs the connector license. There are so many of these ""myths"" with Intelligence I don't think anyone knows.

Looks like it brought it in but under the standard Container (Sage MAS (auto Connect)) not the new container that was made. So the Container came in but the connection was not made and it instead went to the default container. Wondering why that would be.

Without the connector license you can only use the auto connect.

Without the license you can not bring up the connector app which means you can not change or add anything. If you change the license to allow connector and make containers and connections, it will allow you to use them when you change the license to not have connector since the container and connection already exist. The import imports to only one Connection from what I can tell. So I think the issue that I have is Sage made it sound as if a Connection would be made when you import and that is false. It must already exist but any container you create will be created for the customer. So I guess that would be a Half truth on Sage's side. Unless I am missing something.

OK so for reference for anyone else trying to user your connector to create a report that uses a new connection to a different data source, It isn't going to work. You must import it in to one connector and then use the connector UI to create the new connection and move your imported in containers to the new connection. If anyone knows of a better way to do this please let me know but this fixed my issue. The customer can use two different containers even if they do not have connector license, if the Connection already exist with the right containers in them.