6/30/2025 1:29:37 PM
|
| |
| 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.
|
|
|
|
Advice
Posted: 11 May 10 6:23 AM
|
We have a few developers working on saleslogix.
Developer 1 has just changed the account details screen using visual web developer and has inserted the files in the relevant support files/smart parts folder (Portal Manager)
Developer 2 does not know about this file so makes changes to the Account Details form (Entity Manager) but will never see his changes as it does not affect the file above (We will be using Git for a repository but this will not make a difference as the forms to not change each other)
has anybody come accross this problem, and if so how did you avoid it? |
|
|
|
Re: Advice
Posted: 11 May 10 9:17 AM
|
First of all, the Account Details form out of the Box cannot be directly modified on .Net because it will get rebuilt on each deployment.
If Developer 1 modified it, he needed to have loaded the modified file into the VFS under Support Files, and then modified the Pages to point to the Custom part (that he just created).
Now, most important than anything, if you have multiple developers, you should:
- Not work out of the VFS stored on the DB.
- Have each Developer extract a copy of the VFS
- Add source Control to the VFS
Based on your scenario, it appears as if you have several things going on here that are causing problem.
Even if a single developer was working on the Account Details, if he/she does not know how to make the Quick Form into a Custom Part, then every time he/she deployes the changes will be lost.
Additionally, if you have an additional developer loading the same VFS, some changes will be stored depending on who had it open last.
Also, the build will be based on what was loaded, so at the very least Developer 2 should refresh the VFS.
Bottom line, Implement Source Control and properly Configure your environment for Multiple Developers, and make sure that they understand how to modify a Quick Form via VS and then loaded into App Architect as a Custom Part. |
|
|
|
Re: Advice
Posted: 12 May 10 6:16 AM
|
If you're using Git I'll assume that you're using a local repository and local workspace for each developer (I assume that, because that's how we do it and it works well).
The only problem, it seems, is that Developer 1 hasn't informed the other developer(s) that they've changed which form will be used on the Account Details page. The only way around this is for your developers to communicate. If Developer 1 makes a change like that, they should send a quick e-mail or IM to the other developer(s) to let them know the binding has changed, they can then move any of their relevant development into the correct file. Source control isn't a replacement for developer communication 
As an aside, if possible it's probably better not to make QuickForms custom, but I'm sure you have a good reason for doing it that way. We made our ContactDetails custom and it made our life so much harder that eventually I spent a few hours merging our custom version back into the QuickForm 
Hope that helps! |
|
|
|
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!
|
|
|
|
|
|
|
|