8/18/2025 12:27:24 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss the use of the SalesLogix Web Platform, Client and Customer Portals, and the Application Architect (For version 7.2 and higher only). View the code of conduct for posting guidelines.
|
|
|
|
v7.5 - Entity Relationship problem
Posted: 30 Apr 09 1:33 PM
|
I don't know if this is common knowledge to those who are more experienced with SLX 7.5 web development than I, but it took SLX support a number of weeks to figure it out. As such, it may be worth posting.
I created an Entity that had a 1:M relationship from Account. After I created the 1:M relationship (for example, "cPSOneToMany"), I could build and deploy the portal. When logging into the portal, I would get a .Net crash in the event log, and my screen would immediatley display an error that stated "Unable to locate ... _CPSOneToMany".
After a number of people at Sage looked at the problem, someone finally commented on the fact that the first letter in the name of my relationship was lower case. Apparently the build and deploy process was converting the relationship name to uppercase. When the portal was trying to find the uppercase relationship, it did not exist.
All of the troubleshooting that we did to try and remedy this problem really banged up my development environment. We got to the point where we could not even delete the "problem" entities because the code couldn't "cleanly" remove them from the database. Eventually I snapped my development server back to a clean state and started the upgrade again from scratch.
So ... be cautious about case sensitivity when creating relationships in the App Architect. That idea may be apparent to some developers, but it wasn't to me, and nobody at Sage could quickly tell me that was my problem when my upgrade came to a screeching halt. Luckily fo rme, they stuck with the research and eventually came up with an answer (thanks again to Carla for her help).
Jim M. |
|
|
| |
|
Re: v7.5 - Entity Relationship problem
Posted: 01 May 09 3:49 AM
|
Yes good to know - I am always quite sensitive when it comes to case (no pun intended), thanks to Javascript and C# for that!!
Another funny thing that can happen we have noticed is if the case is different on primary keys of a table (I mean in the data itself, not the primary key name), the join fails. We have an external service that generates Id's with an upper case T for example - slx is creating with a lowercase t so the the child records didnt show up. So T6UJ9A000001 and t6UJ9A000001 will not match...
Thanks,
Nick |
|
|
|
Re: v7.5 - Entity Relationship problem
Posted: 01 May 09 3:49 AM
|
Yes good to know - I am always quite sensitive when it comes to case (no pun intended), thanks to Javascript and C# for that!!
Another funny thing that can happen we have noticed is if the case is different on primary keys of a table (I mean in the data itself, not the primary key name), the join fails. We have an external service that generates Id's with an upper case T for example - slx is creating with a lowercase t so the the child records didnt show up. So T6UJ9A000001 and t6UJ9A000001 will not match...
Thanks,
Nick |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|