11/26/2024 4:27:14 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 writing script in Architect plugins for SalesLogix & general SalesLogix customization topics (for Windows client only). View the code of conduct for posting guidelines.
|
|
|
|
Auto display of form control data mappings
Posted: 13 Oct 06 6:25 PM
|
fiogf49gjkf0d Does anyone know how I can accomplish displaying the name of the database field that each control is mapped to on screen. I am tasked with documenting a Saleslogix system of substantial size and need to create a listing of the fields that are used on each screen so that I can compile them in a developers manual. I started to do it manually and then realized how much work would be involved. If there is a way perhaps to extract the field names and compile them into a data grid that would work as well. I need to collect the basics (control name, database field, control type if possible).
Are there any utilities out there that anyone knows about or a suggestion on how I could accomplish this in code?
Thanks... |
|
|
|
Re: Auto display of form control data mappings
Posted: 13 Oct 06 7:33 PM
|
fiogf49gjkf0d The only thing I know of that comes close is Electrician (http://www.jh3.com/software/electrician.htm). You have to decode the "sub-objects" in each plugin's BLOB and Electrician is the only tool I know of that can do it reliably. I've only used the free version, so I'm not entirely sure how easy it'll be to use on a large documentation project.
Having said that I'll relate my personal endeavour. I was tasked with converting a legacy customization into VBScript but I wanted to make sure I only used fields that were necessary. I queried the database looking for values that had a NULL or random bits of data that were unnecessary. I gathered a list of such fields and got with people to make sure I wasn't removing anything that was needed. Then when it came time to redo the screens I knew exactly which fields I could use and made sure all of them were linked up. This was a system that had been in operation for YEARS, so any fields not used weren't going to be used.
Chances are whatever is in the database is a fairly accurate representation of the fields you need in the customization and it eliminates any duplicate controls that may be copied accross tabs or panels. |
|
|
|
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!
|
|
|
|
|
|
|
|