Cool

All fixed. Reinstall of 1.6.5 did the trick. Thanks.

Keith Chisarik

Yeah, this is one of the tables structures that we changed.  Let me know if you don't get it going.

I see table structure changes between the working and non-working for table "DTEproject_item_exceptions" that seems to hold the customization data. I'll try that in the AM.

Keith Chisarik

I am still fighting this, no resolution as of yet. I will reinstall 1.6.5 at customer site to make sure the database is updated, unless you can tell me how to check the current version of the Strataframe database?

Keith Chisarik

It sounds like you just did not have the database up to date.  We added a few fields in 1.6.5...so that is probably what you were fighting.

Yes if I point back to the original database everything is fine, I did realize that I would have to recreate the project data, it let me redfine the BO's and everything I needed to do EXCEPT the customization. It just ignores and changes I make in the edit customizations screen.

The new database will be the master from now on, I have VPN access to it.

Keith Chisarik

Well, it is possible that your SF database is not up to date, but the issue here is that you created the custom code in Database 1 and are now wanting to work on Database 2.  So that code that was in DB1 is not going to be there.  If you set your data source base to DB1, do you get your stuff back?

That is the first thing I would make sure of.  Then...well...we can try to come up with the best solution for working like this.

1) My banaid broke. I changed the SF Data Store for the project from my SQL Server to my customers as they want to start "helping" and now I cannot set any custom properties on the fields in the mapper, they simply dont "stick". Could this happen if the Strataframe database was not up to date? If so, how can one tell if it is up to date or not? I think it should be but am not 100% sure.

If not, what might be causing this, I need my bandaid back as it is not clear to me what the underlying problem is.

2) Field_ITREPORT_Descriptor is making the call to the get  for Public Property [ITREPORT]() As System.String

Keith Chisarik

Sounds good.  I know that something is trying to pull the value on the AddNew or Navigated....something along those lines.  So just to prevent any downstream issues it would definitely be a good idea