SRs with custom SR Numbers, inserted via WS: impact analysis
In our system Service Request records are created with custom numbering of the SR (i.e. value in the standard field SR Number). We ensure that the custom SR numbers are unique. We use webservices quite heavily, lots of objects on the UI as well, many workflows, advanced field management and assignment rules.
I would like to make a list of the potential issues/impacts to be kept in mind for a CRMOD system where the SR records have a custom SR Number. Eg, performance in reports, performance of navigation in the UI. In general, is the SR Number used within CRMOD for any internal processes, or is it just one of the indexed fields for UI purposes?