x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 1 reply
  • Subscribers 74 subscribers
  • Views 160 views
  • Users 0 members are here
Browse Forums
Announcements
106
topics
32
replies
General Discussion
6k
topics
18k
replies
Realisable Software Ltd

SageCRM Dev. Team - Please fix the inconsistencies in the data dictionary.

Posted By

Who knows, this could be miraculously fixed in 7.3 (a project which we just about to undertake).

a. Aside from some fields in the Users table, EVERY single other field in the CRM database should have an entry in custom_edits...this include the meta_data fields present in the various 'custom_' tables, parm_name AND the various fields in the link tables (PhoneLink, EmailLink, PersonLink).

b. Expose the Link entities automatically to both Webservices & SData (why are the primary entities exposed, but these not be default).

c. Stop the arbitrariness! E.g. The Account is available to webservices, but not SDATA (not sure how we actually get this entity exposed to SDATA). The oppo_opportunityid should return the oppo_opportunityid field AND NOT the description.

Having spoken to other (more active) 3rd party CRM developers and they have similar, if not identical complaints, and given that we raised these issues in 7.0/7.1 and they're still not fixed in the latest 7.2 patch.

Thanks

  • 0

    James

    I'll forward to my colleagues in both Product Management and Development.

    Some things maybe bugs and errors. I think that if I remember correctly the release notes for Sage CRM 7.3a mention a fix for an SData issue.

    But some of the things that you wish would be otherwise are because of design decisions that have been made in the past. If you feel that there are some specific areas that need fixing then then the first thing you need to do is log a case. This is important because cases logged through the support desks have an SLA associated with them and they have a much higher priority than a community post about the subject.

    I know from experience that you need to be very precise when logging a case as it has to be a single clearly identifiable and reproducible issue for a Support team to be able log accurately it and escalate this to Dublin.

    The second thing that you should do is post your suggestions on the Ideas Hub.

    community.sagecrm.com/.../default.aspx

    The ideas hub is followed by the Product Management team very closely and it is a good way of suggesting how Sage CRM can be improved to remove some of the inconvenience you may face.

    I have been writing about how Sage CRM is currently in transition. I have a current series of articles that are being published called "Sage CRM's RESTful API: SData for Cloud and On-Premise". This series will explain some of the feature differences between the SOAP web services and SData and how they use Meta Data. It will also look at the move to SData 2.0 and the introduction of full CRUD capabilities. As part of that and the need to be backwardly compatible with SData 1.0 it will explain why some of the intersection tables are not exposed by default.

    See: community.sagecrm.com/.../sage-crm-39-s-restful-api-sdata-for-cloud-and-on-premise-part-1-of-10.aspx

*Community Hub is the new name for Sage City