SharePoint Online Import Service
- or -
Post a project like this€1.5k(approx. $1.6k)
- Posted:
- Proposals: 12
- Remote
- #3457407
- OPPORTUNITY
- Expired
PPH #1 Service Provider in Development & IT : Wordpress|Magento|React Native|Mobile App Development|Angular|Node.js
Mohali
SharePoint Developer, Power Apps, Power Automate and MS Teams Consultant, Office 365 Solution Associate
London
SharePoint & Office 365 Setup & Customization | REST API | SPFx | PnP (js | PowerShell | Controls | Provisioning) | Power Automate | JavaScript | jQuery | React
Porbandar
PPH #1 "Top Rated" Service Provider in Development & IT : Wordpress, Shopify, Magento, Squarespace, ZOHO, WHMCS, Salesforce, Vtiger, Learndash, Moodle
Kenwick
Web Development, Application Development, Mobile app development, Video Streaming Platform
Kolkata
Logo & Graphic Designer / illustration / PowerPoint / CAD / AI Expert / Web Designer
Rawalpindi
128342278364780468130963321588402537323270183031525316277123638476766081736616057
Description
Experience Level: Expert
Project Background
Our Client has an existing property management platform developed on SharePoint Online.
Our Client wants to import a list of Bank Transactions (exported manually from an online bank
platform) weekly into the existing platform.
We need a solution where;
a. Transactions imported are listed against a property where the reference numbers match
b. Transactions can be manually assigned to a property where the reference numbers don't match
c. Duplicate checking mechanism for transactions
I have detailed several high-level points below;
1. The ideal process for importing financial transactions into SharePoint online – existing list(s) and sub-list requirement.
o The financial transactions will be exported to a file from the bank's online portal. The export file will have property reference codes against some transactions. Once uploaded to the SharePoint document library, the transactions file will need to be copied into two new sub-lists: one where a match was found and the second where no match was found.
2. The requirement to match imported data against existing data based on 'Reference Number.'
o Once the spreadsheet is uploaded to this document library, the importer will copy the data from the spreadsheet and match the records based on the property reference number with the 'Unit/Property' SharePoint list. This list contains a complete list of properties with their reference numbers. Once the importer app finds a match, the matched transactions will then be moved to another sub-list called 'Transaction,' and where a match was not found, the records will be transferred to a SharePoint sub-list called 'Flagged Transactions.'
3. The solution must ensure that duplicate transactions are flagged/disregarded
o The importer app will need to identify duplicate transactions when the data is being copied over to the SharePoint lists based on the following three items 1) Property Reference Number, 2) Transaction Reference number, 3) Transaction Amount; and 4) Transaction Date. The duplicate records need to be highlighted in Red in the 'Flagged Transactions' list.
4. Transactions that 'match' must be tagged as 'matched' with unallocated transactions labeled 'unmatched.'
o There will be a status column in SharePoint sub-lists - 'Transaction' and 'Flagged Transactions.' When the importer finds a match and copies the record over to the 'Transaction' list, the status column should be populated with the text 'Matched.' Where a match is not found, the transaction needs to be copied to the ' Flagged transaction list.' The status column needs to be populated with the text 'Unmatched.' Also, when a match is found, the importer app needs to resolve the lookup field for the 'Property name' lookup field and map the correct property name against that transaction.
Our Client has an existing property management platform developed on SharePoint Online.
Our Client wants to import a list of Bank Transactions (exported manually from an online bank
platform) weekly into the existing platform.
We need a solution where;
a. Transactions imported are listed against a property where the reference numbers match
b. Transactions can be manually assigned to a property where the reference numbers don't match
c. Duplicate checking mechanism for transactions
I have detailed several high-level points below;
1. The ideal process for importing financial transactions into SharePoint online – existing list(s) and sub-list requirement.
o The financial transactions will be exported to a file from the bank's online portal. The export file will have property reference codes against some transactions. Once uploaded to the SharePoint document library, the transactions file will need to be copied into two new sub-lists: one where a match was found and the second where no match was found.
2. The requirement to match imported data against existing data based on 'Reference Number.'
o Once the spreadsheet is uploaded to this document library, the importer will copy the data from the spreadsheet and match the records based on the property reference number with the 'Unit/Property' SharePoint list. This list contains a complete list of properties with their reference numbers. Once the importer app finds a match, the matched transactions will then be moved to another sub-list called 'Transaction,' and where a match was not found, the records will be transferred to a SharePoint sub-list called 'Flagged Transactions.'
3. The solution must ensure that duplicate transactions are flagged/disregarded
o The importer app will need to identify duplicate transactions when the data is being copied over to the SharePoint lists based on the following three items 1) Property Reference Number, 2) Transaction Reference number, 3) Transaction Amount; and 4) Transaction Date. The duplicate records need to be highlighted in Red in the 'Flagged Transactions' list.
4. Transactions that 'match' must be tagged as 'matched' with unallocated transactions labeled 'unmatched.'
o There will be a status column in SharePoint sub-lists - 'Transaction' and 'Flagged Transactions.' When the importer finds a match and copies the record over to the 'Transaction' list, the status column should be populated with the text 'Matched.' Where a match is not found, the transaction needs to be copied to the ' Flagged transaction list.' The status column needs to be populated with the text 'Unmatched.' Also, when a match is found, the importer app needs to resolve the lookup field for the 'Property name' lookup field and map the correct property name against that transaction.
Karl M.
100% (2)Projects Completed
2
Freelancers worked with
2
Projects awarded
0%
Last project
25 Jan 2019
Ireland
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies