Please submit all product enhancement ideas below. We welcome your feedback; your ideas will be reviewed by the Product Manager that oversees the development of that part of the product on an ongoing basis and updated with its current status monthly based on our product planning process. Ideas you submit could help us shape features currently in development or grow our repository of requirements for our next big enhancement. Thank you for taking the time to share your thoughts and expertise with us.
If you believe you are experiencing a defect please contact Support.
From a LO/CRM Sync tool (v 2.6) to CRM 4.0, when we hit a failure (i.e. "operation has timed out" or an "unexpected exception") develop a way to "auto" queue up these failures for reprocessing in the next sync. This will remove the action for the client to manually select the record to be reprocessed, for each and ever record that fails. If the record "Failed", reprocessing in all instances is warranted since an operation timeout or unexpected exception are not issues resolved by "fixing" a record, but rather issues related to system performance/available resources.
Having the records sit as "failed" and don't queue for reprocess currently - unless manually keyed/clicked creates issues with revenue applying to a record. If the record wasn't created due to a "failure" then the revenue cannot commit to CRM.
|Area of the Product||API's|
|Org/Company Name||Save The Children USA|