Business Object Designer

Cannot find 'CompanyID' in CContact class

I am developing a web page for new contact registering. The problem is that I cannot assign a company ID to a new contact. I found there's a field called 'company_id' in 'Contact' table, but in .net, the 'CContact' class has no such property. I wonder where and how I can make this field available for web pages?

Thanks.
Michael

New name(s) for iBO

Is it just me, or are all the "business object" named things starting to become confusing? Here's the ones I can count:

  • The original COM-based iBO
  • iBO for .NET
  • The core Business Objects which make up iMIS
  • Business Object Builder, Business Object Architect, Business Object Designer, or whatever else it becomes
  • Stephen Moseley's iBO Wrapper
  • The Active Matter iBO Wrapper

Things to try when .NET components error

Over the last 18 months or so as we have deployed the iMIS .NET server at clients and then tried to roll out components like IQA, etc to certain users, we (sorry, I wiped out the authors name accidentally) have experienced a variety of environment-related problems to which we have employed a variety of environment-related solutions. I was hoping that somewhere there existed or we could create (here perhaps) a definitive list of things to investigate / try when the rather inexpressive iMIS .NET error page pops up.

Note on effective use of disconnected data

So, Stacey and I where chasing down this bug where when you added a PackageItem to a SourceCode's Package, only the first got added. Well... Until someone came back to the page and found that they had been added, they just never showed up in the list. It reaked of disconnected data caching issues.

Turns out, the issue was adding a PackageItem object that points to a Supplement Object that did not exist in the container. Once the SourceCode.GetSupplements() method was called it (correctly) set the ChildLoaded for Supplements to true, so subsequent calls to the Method would never check the DB for the underlying Supplement Object, and wouldn't hit the db to find it (since ChildLoaded was set to true for supplements), but it would add the PackageItem object since that only needed the key. In other words,

#1 SourceCode.GetPackageItems();
#2 SourceCode.AddPackageItem(key);
#3 SourceCode.GetPackageItems();

#3 DID NOT end up returning the PackageItem added on #2.