Skip to main content
Solved

GIS FC (FGDB) to Excel Spreadsheet

  • September 16, 2025
  • 1 reply
  • 27 views
hawaiialex
Contributor
Forum|alt.badge.img+4

Hi folks,

Trying my hand at a workflow that takes certain records from a GIS feature class and writes them into a Spreadsheet XLSX (2025 Work Plan). 

I’ve renamed the attributes from the GIS feature class schema to match the relevant fields in the 2025 Work Plan Spreadsheet with no issues. When I examine them, they look good in the table.

The Spreadsheet has certain Excel-only fields that are not included in the GIS feature class. What I am finding is that while the information is being translated into the 2025 Work Plan Excel Sheet, it is also writing the remainder of the fields from the GIS feature class into columns in the 2025 Work Plan Excel Sheet that are Excel-only.

This is despite trying to remove the excess fields in the Writer. And even mapping the fields directly to the corresponding fields in the Excel Writer. I had tried experimenting with the ‘Update’ parameter rather than Insert, but that caused errors.

Are there any suggestions to ensure only the specified GIS fields are written into the WorkPlan Spreadsheet and the excel only fields within the spreadsheet are left alone and not touched?

Thanks everyone!

Best answer by hawaiialex

After much tinkering I found that the solution was to add an AttributeCreator to add the Excel-only fields and leave them as blank values. Then to include the same newly created Excel-only fields in the AttributeKeeper as well as in the Writer when set to ‘Manual’ and populating the fields in a way that matches the schema/order of how they appear in the Excel spreadsheet. 

 

This worked and the Excel only columns aren’t touched as expected.

    danilo_fme
    This post is closed to further activity.
    It may be an old question, an answered question, an implemented idea, or a notification-only post.
    Please check post dates before relying on any information in a question or answer.
    For follow-up or related questions, please post a new question or idea.
    If there is a genuine update to be made, please contact us and request that the post is reopened.

    1 reply

    hawaiialex
    Contributor
    Forum|alt.badge.img+4
    • hawaiialexContributor
    • Author
    • Contributor
    • Best Answer
    • September 17, 2025

    After much tinkering I found that the solution was to add an AttributeCreator to add the Excel-only fields and leave them as blank values. Then to include the same newly created Excel-only fields in the AttributeKeeper as well as in the Writer when set to ‘Manual’ and populating the fields in a way that matches the schema/order of how they appear in the Excel spreadsheet. 

     

    This worked and the Excel only columns aren’t touched as expected.

    Community Stats

    32,128
    Posts
    121,963
    Replies
    39,779
    Members

    Latest FME

    Terms & ConditionsCookie settingsAccessibility statement
    A product of
    Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.