In the attached image you can see a disabled database connection entry in the Relink popup of a datasource. The mouse pointer is not showing in the image, but it is a red forbidden icon.

I can not select the database connection, nor does the OK button ever become enabled.

But when I doubleclick the connection, voilà, my database connection is happily used.

Perhaps that is not how it should be.

------------------------------
Reinier Battenberg
https://github.com/CognosExt
------------------------------

#CognosAnalyticswithWatson

Reinier,

​When creating a data source, you can create a connection or multiple connections under the data source.

It looks like you disable at the data source level.  I suggest you disable at the connection level.

------------------------------
KIAN GOH
------------------------------

Original Message:
Sent: 01-31-2019 04:53 AM
From: Reinier Battenberg
Subject: Relinking datasource shows disabled sources unnecessarily

In the attached image you can see a disabled database connection entry in the Relink popup of a datasource. The mouse pointer is not showing in the image, but it is a red forbidden icon.

I can not select the database connection, nor does the OK button ever become enabled.

But when I doubleclick the connection, voilà, my database connection is happily used.

Perhaps that is not how it should be.

------------------------------
Reinier Battenberg
https://github.com/CognosExt
------------------------------

#CognosAnalyticswithWatson

My apologies for not being complete and clear.

The disabled state of a connection only happens:

- When I want to relink my datamodule to the *same* datasource as it has been initially. I want this because during development I keep changing details in the database and in order to load the new fields or tables, I need to reload the connection metadata, and then relink the original source connection to the datamodule that is using it.
- The connection that shows disabled, is not disabled. It is very active, and I can select it, by double-clicking it. And only by double-clicking it.

So, either I do not have to relink my source to my datamodule when I update my connection metadata (and just be more patient), but then why allow the double-click? Or the UI shows the connection disabled whereas it should be enabled, because it is a valid action to 'relink' a connection.

rgds,
Reinier

------------------------------
Reinier Battenberg
https://github.com/CognosExt
------------------------------

Original Message:
Sent: 02-04-2019 07:41 AM
From: KIAN GOH
Subject: Relinking datasource shows disabled sources unnecessarily

Reinier,

​When creating a data source, you can create a connection or multiple connections under the data source.

It looks like you disable at the data source level.  I suggest you disable at the connection level.

------------------------------
KIAN GOH

Original Message:
Sent: 01-31-2019 04:53 AM
From: Reinier Battenberg
Subject: Relinking datasource shows disabled sources unnecessarily

In the attached image you can see a disabled database connection entry in the Relink popup of a datasource. The mouse pointer is not showing in the image, but it is a red forbidden icon.

I can not select the database connection, nor does the OK button ever become enabled.

But when I doubleclick the connection, voilà, my database connection is happily used.

Perhaps that is not how it should be.

------------------------------
Reinier Battenberg
https://github.com/CognosExt
------------------------------

#CognosAnalyticswithWatson

Reinier,

In Cognos 11.1.1, I created a data source, inside the data source, I created a connection.  
ie: 
Data source 1         <======  Scenario 2: Disable at this level
           |
           ----->    connection 1     <======  Scenario 1: Disable at this level

Scenario 1:  Disable only the connection
If I disable the "connection 1", when I create new data module (or attempt to relink) and selected "data source 1", a toast message "Your content can't be loaded. Try again or contact your system administrator." will show up.  I don't see any option or able to double click to proceed. This is an expected behavior. 

Scenario 2: Disable only the data source
If I disable the "data source 1", when I create new data module (or attempt to relink), I see  "data source 1" shows red forbidden icon. I can double click to select the schema into creating data module. From there, I observe I could access data, which I think is not the correct behavior. I logged a defect 266394 to have this issue looked at.


Please log a support ticket if you need further assistance.

------------------------------
KIAN GOH
------------------------------

Original Message:
Sent: 02-04-2019 08:51 AM
From: Reinier Battenberg
Subject: Relinking datasource shows disabled sources unnecessarily

My apologies for not being complete and clear.

The disabled state of a connection only happens:

- When I want to relink my datamodule to the *same* datasource as it has been initially. I want this because during development I keep changing details in the database and in order to load the new fields or tables, I need to reload the connection metadata, and then relink the original source connection to the datamodule that is using it.
- The connection that shows disabled, is not disabled. It is very active, and I can select it, by double-clicking it. And only by double-clicking it.

So, either I do not have to relink my source to my datamodule when I update my connection metadata (and just be more patient), but then why allow the double-click? Or the UI shows the connection disabled whereas it should be enabled, because it is a valid action to 'relink' a connection.

rgds,
Reinier

------------------------------
Reinier Battenberg
https://github.com/CognosExt

Original Message:
Sent: 02-04-2019 07:41 AM
From: KIAN GOH
Subject: Relinking datasource shows disabled sources unnecessarily

Reinier,

​When creating a data source, you can create a connection or multiple connections under the data source.

It looks like you disable at the data source level.  I suggest you disable at the connection level.

------------------------------
KIAN GOH

Original Message:
Sent: 01-31-2019 04:53 AM
From: Reinier Battenberg
Subject: Relinking datasource shows disabled sources unnecessarily

In the attached image you can see a disabled database connection entry in the Relink popup of a datasource. The mouse pointer is not showing in the image, but it is a red forbidden icon.

I can not select the database connection, nor does the OK button ever become enabled.

But when I doubleclick the connection, voilà, my database connection is happily used.

Perhaps that is not how it should be.

------------------------------
Reinier Battenberg
https://github.com/CognosExt
------------------------------

#CognosAnalyticswithWatson

The thing is: my connections on any level are *not* disabled. I never disabled anything. I am just wondering why Cognos *shows* my connection as disabled, where it is not.

------------------------------
Reinier Battenberg
https://github.com/CognosExt
------------------------------

Original Message:
Sent: 02-04-2019 05:06 PM
From: KIAN GOH
Subject: Relinking datasource shows disabled sources unnecessarily

Reinier,

In Cognos 11.1.1, I created a data source, inside the data source, I created a connection.  
ie: 
Data source 1         <======  Scenario 2: Disable at this level
           |
           ----->    connection 1     <======  Scenario 1: Disable at this level

Scenario 1:  Disable only the connection
If I disable the "connection 1", when I create new data module (or attempt to relink) and selected "data source 1", a toast message "Your content can't be loaded. Try again or contact your system administrator." will show up.  I don't see any option or able to double click to proceed. This is an expected behavior. 

Scenario 2: Disable only the data source
If I disable the "data source 1", when I create new data module (or attempt to relink), I see  "data source 1" shows red forbidden icon. I can double click to select the schema into creating data module. From there, I observe I could access data, which I think is not the correct behavior. I logged a defect 266394 to have this issue looked at.


Please log a support ticket if you need further assistance.

------------------------------
KIAN GOH

Original Message:
Sent: 02-04-2019 08:51 AM
From: Reinier Battenberg
Subject: Relinking datasource shows disabled sources unnecessarily

My apologies for not being complete and clear.

The disabled state of a connection only happens:

- When I want to relink my datamodule to the *same* datasource as it has been initially. I want this because during development I keep changing details in the database and in order to load the new fields or tables, I need to reload the connection metadata, and then relink the original source connection to the datamodule that is using it.
- The connection that shows disabled, is not disabled. It is very active, and I can select it, by double-clicking it. And only by double-clicking it.

So, either I do not have to relink my source to my datamodule when I update my connection metadata (and just be more patient), but then why allow the double-click? Or the UI shows the connection disabled whereas it should be enabled, because it is a valid action to 'relink' a connection.

rgds,
Reinier

------------------------------
Reinier Battenberg
https://github.com/CognosExt

Original Message:
Sent: 02-04-2019 07:41 AM
From: KIAN GOH
Subject: Relinking datasource shows disabled sources unnecessarily

Reinier,

​When creating a data source, you can create a connection or multiple connections under the data source.

It looks like you disable at the data source level.  I suggest you disable at the connection level.

------------------------------
KIAN GOH

Original Message:
Sent: 01-31-2019 04:53 AM
From: Reinier Battenberg
Subject: Relinking datasource shows disabled sources unnecessarily

In the attached image you can see a disabled database connection entry in the Relink popup of a datasource. The mouse pointer is not showing in the image, but it is a red forbidden icon.

I can not select the database connection, nor does the OK button ever become enabled.

But when I doubleclick the connection, voilà, my database connection is happily used.

Perhaps that is not how it should be.

------------------------------
Reinier Battenberg
https://github.com/CognosExt
------------------------------

#CognosAnalyticswithWatson

Reinier,

I apologize for misunderstanding your question. If your data source/connection is *not* disabled, I don't expect you to see an disabled icon. Please log a support call to have the issue look at.

------------------------------
KIAN GOH
------------------------------

Original Message:
Sent: 02-05-2019 03:47 PM
From: Reinier Battenberg
Subject: Relinking datasource shows disabled sources unnecessarily

The thing is: my connections on any level are *not* disabled. I never disabled anything. I am just wondering why Cognos *shows* my connection as disabled, where it is not.

------------------------------
Reinier Battenberg
https://github.com/CognosExt

Original Message:
Sent: 02-04-2019 05:06 PM
From: KIAN GOH
Subject: Relinking datasource shows disabled sources unnecessarily

Reinier,

In Cognos 11.1.1, I created a data source, inside the data source, I created a connection.  
ie: 
Data source 1         <======  Scenario 2: Disable at this level
           |
           ----->    connection 1     <======  Scenario 1: Disable at this level

Scenario 1:  Disable only the connection
If I disable the "connection 1", when I create new data module (or attempt to relink) and selected "data source 1", a toast message "Your content can't be loaded. Try again or contact your system administrator." will show up.  I don't see any option or able to double click to proceed. This is an expected behavior. 

Scenario 2: Disable only the data source
If I disable the "data source 1", when I create new data module (or attempt to relink), I see  "data source 1" shows red forbidden icon. I can double click to select the schema into creating data module. From there, I observe I could access data, which I think is not the correct behavior. I logged a defect 266394 to have this issue looked at.


Please log a support ticket if you need further assistance.

------------------------------
KIAN GOH

Original Message:
Sent: 02-04-2019 08:51 AM
From: Reinier Battenberg
Subject: Relinking datasource shows disabled sources unnecessarily

My apologies for not being complete and clear.

The disabled state of a connection only happens:

- When I want to relink my datamodule to the *same* datasource as it has been initially. I want this because during development I keep changing details in the database and in order to load the new fields or tables, I need to reload the connection metadata, and then relink the original source connection to the datamodule that is using it.
- The connection that shows disabled, is not disabled. It is very active, and I can select it, by double-clicking it. And only by double-clicking it.

So, either I do not have to relink my source to my datamodule when I update my connection metadata (and just be more patient), but then why allow the double-click? Or the UI shows the connection disabled whereas it should be enabled, because it is a valid action to 'relink' a connection.

rgds,
Reinier

------------------------------
Reinier Battenberg
https://github.com/CognosExt

Original Message:
Sent: 02-04-2019 07:41 AM
From: KIAN GOH
Subject: Relinking datasource shows disabled sources unnecessarily

Reinier,

​When creating a data source, you can create a connection or multiple connections under the data source.

It looks like you disable at the data source level.  I suggest you disable at the connection level.

------------------------------
KIAN GOH

Original Message:
Sent: 01-31-2019 04:53 AM
From: Reinier Battenberg
Subject: Relinking datasource shows disabled sources unnecessarily

In the attached image you can see a disabled database connection entry in the Relink popup of a datasource. The mouse pointer is not showing in the image, but it is a red forbidden icon.

I can not select the database connection, nor does the OK button ever become enabled.

But when I doubleclick the connection, voilà, my database connection is happily used.

Perhaps that is not how it should be.

------------------------------
Reinier Battenberg
https://github.com/CognosExt
------------------------------

#CognosAnalyticswithWatson