Missing fields when using SharePoint Source Component
Scenario:
My custom created SharePoint fields are missing when using the SharePoint Source component
Solution:A possible solution to the issue is to include the hidden fields. You should follow the steps below:
- Click twice on the SharePoint Source Component to get the SharePoint Source Editor to open.
- Check the "Include Hidden Fields" box. Look at the screenshot below:
- Click the button "OK" to close the SharePoint Editor
- Verify that the missing fields showed up
Book a Presales Call
Related Articles
Missing fields when using SharePoint Source Component
Scenario: My custom created SharePoint fields are missing when using the SharePoint Source component Solution: A possible solution to the issue is to include the hidden fields. You should follow the steps below: Click twice on the SharePoint Source ...Missing fields when using SharePoint Source Component
Scenario: My custom created SharePoint fields are missing when using the SharePoint Source component Solution: A possible solution to the issue is to include the hidden fields. You should follow the steps below: Click twice on the SharePoint Source ...Missing fields when using SharePoint Source Component
Scenario: My custom created SharePoint fields are missing when using the SharePoint Source component Solution: A possible solution to the issue is to include the hidden fields. You should follow the steps below: Click twice on the SharePoint Source ...Missing fields when using SharePoint Source Component
Scenario: My custom created SharePoint fields are missing when using the SharePoint Source component Solution: A possible solution to the issue is to include the hidden fields. You should follow the steps below: Click twice on the SharePoint Source ...How to know if a column is missing in my excel file when using Excel Source Plus component?
If a column is missing in your excel file when using the Excel Source Plus component, your SSIS+ package will execute successfully, but we generate a warning message in the package event log. Please look at the screenshot below: