Frosty the Coder
Legendary Poster
I have a custom joined BSVW where the tables were joined in the incorrect order.
I went into design, changed the primary table, and submitted it for DV build/deploy.
Today, I installed that DV package.
When I go into design, the correct table is listed as the primary.
When I look at the SQL statement generated when the BSVW is used,
it appears that my changes did not take effect (or at least not locally).
To address this, I plan on creating a NEW BSVW, w/the tables in the correct sequence,
however I am curious as to why the SQL does not reflect yesterday's change.
Can someone explain this to me?
Thanks
I went into design, changed the primary table, and submitted it for DV build/deploy.
Today, I installed that DV package.
When I go into design, the correct table is listed as the primary.
When I look at the SQL statement generated when the BSVW is used,
it appears that my changes did not take effect (or at least not locally).
To address this, I plan on creating a NEW BSVW, w/the tables in the correct sequence,
however I am curious as to why the SQL does not reflect yesterday's change.
Can someone explain this to me?
Thanks