Import data from Excel spreadsheet using file path provided in excel

Hi,

Hopefully I understood correctly.

I made 3 options.

• one where a file and directory reader is merged with you’r excel. (you could test later if the file excist or not.
• one where I only use a folder and directory reader and filter on the MDB files
• one where only the ecxel is read and it reads the MDB files from the excel information.

I would prefer the first one, so when you have a lot of folders with a lot of different files, and someone adds something in the ecxel, but not in the folder, you can see what file you are missing.

Let me know if this helps you.

Kr

Job

Thanks ​@jobvdnoort 
That was my requirement..

I was successfully able to run it but i cannot the feature or details in MDB , I see in visual preview as No schema..

I should able to read all the data in each feature class wise 

 

I should able to read all the data in each feature class wise for each each and i should write it back with same name to GDB..

Your support highly appreciated

Thanks Again
 

​@evieatsafe 

Thanks for the suggestions and myself and my colleague followed the instructions provided but we couldnt achieve the results.

I have attached you the workspace and sample data 

We are just trying to transfer the MDB data to GDB  stored in different path by reading path from  the excel sheet and pulling the data from that path and then extract the information and transform it to GDB and then store in the similar path..

Thank You so much for the kind support

Thanks Again

Hi ​@adnanyazdani thanks for your workspace that you are working on. You may want to try the MS Access reader instead of the Personal GDB reader to see if this produces different and better results. I also see in your workspace that you have connected an AttributeExposer to the Schema which is curious, you may want to review our articles on working with the SchemaScanner and Dynamic writing. 

Also, you can expose attributes directly in the FeatureReader under Attribute & Geometry Handling > Generic Port > Attributes to Expose. This way you won’t have to use an AttributeExposer.

I also want to mention that even if your Table View when using Feature Cache says <no schema>, you likely still have attributes unexposed in the Feature Information Window. When writing dynamically you do not need to expose these unless you are manipulating the attribute values. As long as you have connected the schema to the writer, either from the FeatureReader or the SchemaScanner, and also specify the Schema Sources and Schema Definition Name. This should write without error. 

It does sound like you are facing errors on reading, so perhaps solve those errors first? What errors are you facing right now? Let me know if you have any follow-up questions.