(1) These two applications are very stable, almost no incidents are reported for both after Chengdu team get ownership from India dev team.
(2) No further development has been done by Chengdu team.

啟動應用後的第一個 batch 請求：

請求明細：

發起請求的程式碼：

後臺 OData 服務實現類：

如何除錯 batch 請求？

注意，batch 請求包含的 operations，後臺是並行處理的，因此一瞬間會彈出多個斷點：

設定屬性的獲取：The retrieval logic is implemented in this method: CL_CRM_SPS_CUSTOMIZING_IMPL~GET_USER_SETTINGS

{"d":{"results":[{"__metadata":{"id":"https://localhost:8090/sap/opu/odata/sap/CRM_SALESPIPELINE_SALESREP/SalesPipelineSettings('WANGJER')","uri":"https://localhost:8090/sap/opu/odata/sap/CRM_SALESPIPELINE_SALESREP/SalesPipelineSettings('WANGJER')","type":"CRM_SALESPIPELINE_SALESREP.SalesPipelineSetting"},"UserName":"WANGJER","OpportunityMaxValue":"10000.00","OpportunityMinValue":"1000.00","OpportunityStepValue":"1000.00","TimeTo":"\/Date(1451520000000)\/","TimeFrom":"\/Date(1420070400000)\/","CurrencyCode":"EUR","SalesTarget":"0.00","SalesTargetPeriodicity":"2","EndOfPeriod":"\/Date(1443571200000)\/","StartOfPeriod":"\/Date(1441065600000)\/","SetValuesManually":true}]}}

 

PeriodicityText in SalesPipeline

year range in Sales Pipeline

Currency List

user status：

How are Opportunities in chart retrieved in backend

My Opportunity 的搜尋實現

根據 employee responsible 搜尋：

更多Jerry的原創文章，盡在："汪子熙":