I have a few customizations I bundled up from v7.5.2.  I simulated the customer's live upgrade as closely as possible in a test environment in moving to v7.5.4.  On the test environment, I was able to effectively apply and build the customizations on top of the v7.5.4 + Mobile 1.1 project.

On the live upgrade, I tried following the same steps.  I received the below error.  On my last attempt, I backed up the full project from the test server and imported into a live project.  Same thing - build failure on Interfaces.  Note that I did clear out the output path in all cases.

As an attempt, I also transferred over the output folder and then just deployed thinking that might help narrow down the problem.  The web customizations show up but the data is not bound (doesn't display data when it has it and doesn't allow new data to be saved).

Any ideas on why this is happening?  Seems like the environment should be the same.  Is it possible I'm missing one or more pieces of data in the database?  Thanks in advance.

ERROR - C:\Documents and Settings\SLXService\Application Data\Sage\Platform\Output\interfaces\IAccount.cs(421,16):The type 'Sage.Entity.Interfaces.IAccount' already contains a definition for 'Owner'

-- 419: [Properties.SRDisplayName("Account.Owner.DisplayName")]

-- 420: [BelongsTo]

-- 421: IOwner Owner { get; set; }

-- 422: ICollection<IReturn> Returns { get; }

-- 423:  [Properties.SRDisplayName("Account.SalesOrders.DisplayName")]

Doubling up of properties does happen from time to time. If you bundle a property from one environment to another sometimes (for a reason I cannot see) it puts the property in twice and you get build errors.

In your scenario I would remove the Account.Owner relationship property, do a build interfaces. Then re-add it and do another build interfaces. Failing that try a full rebuild in between each of those steps.

Thanks,

Nick

Nick,

You have pulled me from the pits of despair.  Thanks for the excellent tip.  As to why I build the project in one environment, then backup the project, restore to a new environment, and then have a failed build... that unfortunately escapes the grasp of my mental powers.  As it turns out, there were two Owner properties set under Account - one under normal properties and one under parent properties.  I removed the "normal" property and the build did in fact succeed.  I won't be able to test this until this evening but I'm feeling optimistic about it.  Thanks again!

C. Burriss

It is strange its under normal properties, but I have actually seen that exact scenario and it was with Owner. Having worked with the web platform since 7.2 beta almost everyday I can make you feel pessimistic once again by saying I have very odd things like this happen on a weekly basis

Last week's: bundle all customisations from one environment to another, yet some of my business rules contained code that was developed weeks ago and had been changed since. It turned out, this is a good one to remember actually, when you get a build error and you double click on the error to bring up the appropriate business rule, you change the code there and it only changes the c# snippet library project that is local on the hard drive (i.e. not in the database/VFS). So the build works fine and is happy, and the deployment contains your latest code. However when you bundle it it grabs the code from the VFS and this is out of date (and actually fails to build again when you install the bundle on the target environment). I am working with a local VFS so this may behave slightly differently when working with the main VFS. That was my weekend gone...

Anyway, glad I could help.

Cheers,

Nick

I hear you.  I love .Net development but I don't like customizing SLX Web too much.  It always gives me grief.  At etiher rate, I was able to deploy the site yesterday and do some testing with the Owner field.  Everything seems to be functioning correctly so that's good news!  Thanks again!

Chris/Nick,

I'd really like to help get you're daily issues resolved with SLX Web Development.  We have made many changes to improve the experience in our next release.  If you have a Top 10 list of issues you would like to improve your development experience I'd love to hear them.  If they are defects reproducible scenarios would help immensely.

thanks for your time,

John Perona

Director Product Development SalesLogix

john dot perona at sage.com

Hi John,

Thanks for reaching out.  I don't know that I have anything in particular in mind at this point but I'll let you know if I come up with anything.  Thanks.

john:

I can consistently create errors with bringing in properties from a bundle....

duplicate fields

slightly different display names

display names with spaces in them

wrong data types.

They don't seem to 'match' up very well with the existing fields.....and if you don't go in an muck with properties you get build errors.

This has been posted many times before up on the SLX Forum.

One thing you might consider: how do you delete a property? I'm talking about the Edit Properties window for an Entity, not the Update Properties Window.

I can change the name (which wreaks holy havoc on the code....), display name, data type....wonderful. But I can't delete the item? Why not?

don't assume you/I haven't created duplicate definitions of the same property....allow me to delete the property. That's the quick way to resolve two Owner properties in one entity once the duplicate properties have been created.

RJ Samp