database substitution issue after upgrading to 9.8.2
Completed
We recently upgraded from 9.7.0.3 to the newly released 9.8.2 and started having data source substitution errors across our platform. Our set up is essentially the same as what was described by this user in this ticket - https://community.yellowfinbi.com/topic/27012-data-source-substitution-issue.
We checked under our child accounts and while all the connection settings seem correct and should be pulling from child schemas, YF still continues to pull from the parent schema.
Seems like this is a known issue? Is this something that was introduced POST version 9.7??? Please advise on what's our best bet now - should we roll back the update?
The same question
Looks like the ticket referenced above was changed or deleted:
Essentially our setup is using data source substitution to switch the primary org's schema out in the child accounts.
For our data source we have multiple views based off of it. Some of the views are working correctly and some are not.
(When looking at the SQL, some views include the schema name and some omit it, even though all are based on the same data source).
I believe all database and schema logic is handled by the data source, not the view, so it is strange that we are not getting consistent behavior among each of the views.
Looks like the ticket referenced above was changed or deleted:
Essentially our setup is using data source substitution to switch the primary org's schema out in the child accounts.
For our data source we have multiple views based off of it. Some of the views are working correctly and some are not.
(When looking at the SQL, some views include the schema name and some omit it, even though all are based on the same data source).
I believe all database and schema logic is handled by the data source, not the view, so it is strange that we are not getting consistent behavior among each of the views.
I our data source setting look like this in the primary org:
(Yet still some views are attaching the primary orgs schema name in the child accounts)
I our data source setting look like this in the primary org:
(Yet still some views are attaching the primary orgs schema name in the child accounts)
Hello Luke,
Greetings of the day!
I can see that there is a another ticket raised for the same issue in our community portal. So we will update you on this ticket ( https://community.yellowfinbi.com/agent/report/5/object/27651)
I will close this and work on that other ticket.
Regards,
Sri Vamsi
Hello Luke,
Greetings of the day!
I can see that there is a another ticket raised for the same issue in our community portal. So we will update you on this ticket ( https://community.yellowfinbi.com/agent/report/5/object/27651)
I will close this and work on that other ticket.
Regards,
Sri Vamsi
@escape road: It looks like the ticket called for above was changed or deleted:
The main way we set up things is by using data source substitution to change the model from the main organization to the child accounts.
We have more than one view based on our info source. There are views that work right and views that don't.
Some views show the model name in the SQL, while others don't. This is true even though all of them use the same data source.
I think the data source, not the view, handles all database and schema code. That's why it's strange that different views don't behave the same way.
@escape road: It looks like the ticket called for above was changed or deleted:
The main way we set up things is by using data source substitution to change the model from the main organization to the child accounts.
We have more than one view based on our info source. There are views that work right and views that don't.
Some views show the model name in the SQL, while others don't. This is true even though all of them use the same data source.
I think the data source, not the view, handles all database and schema code. That's why it's strange that different views don't behave the same way.
Replies have been locked on this page!