48 thoughts on “Flow Screen Component: Create/Update Custom Metadata type Records using CSV and Flow

  1. Pingback: Create Custom Metadata Records from Flow & a CSV File – UnofficialSF

  2. Pingback: Flow Community Development Overview “Flowcast” – Feb. 2021 – UnofficialSF

  3. Pingback: Flow Community Development Overview “Flowcast” – Feb. 2021 – UnofficialSF

  4. Pingback: Create and Manage Custom Metadata Types using Salesforce CLI |  forcePanda

  5. Hello Narender,
    Thank you for your works and efforts
    I’m struggling to update CMDT records using your component in Flow. I was using DeveloperName in the CSV fiel to to map records but couldn’t make it work.
    The component showed error and asked me to check the API name again
    Can you explain a little bit more how to update records?
    Toan

    Like

  6. Hi Narender,
    Thanks for the great effort i used your solution now a coupe of times but now i have a csv which should have UTF-8 encoding. Is there a way to make this solution also compatible with the UTF-8 encoding format?

    Like

  7. Hello – I love the idea of this component. I’m struggling to get it functioning properly though.

    This is the error message I’m receiving when attempting to run the flow via utility bar: “Invalid double: hyd panelCheck console log for more info.”

    I am using a standard csv file, not UTF-8 that others noted above. I can’t figure out where the configuration error is.

    To help aid in troubleshooting:

    I’ve confirmed the contentdocumentId and cmdt api names are accurate. I was initially also getting a couple errors with respect to column names that I resolved as well. I’ve ensured that DeveloperName and MasterLabel are populated and unique.

    Thank you for any support! Really excited about getting this put together correctly!

    Like

      • Hello again – thanks for the fast reply. I have gotten past that error – so thank you for giving me a specific cell to look at it. The mistake was that there were commas in that cell of text.

        After removing all commas and reaffirming the end column didn’t have any blank values, CMDT API Names of fields were column headers and all fields were ‘text’ (no dates in my csv), I received this error:

        Salesforce System Error: 1408020708-333373 (1188083556) (1188083556)Check console log for more info.

        Probably obvious to others, but just want to note if anyone else runs into this; I resolved the above error by limiting my record creation to 100 records, and was successful.

        Thank you so much! This is going to save a ton of time for our team!

        Like

  8. Hi Narender.
    I was using this screen component for uploading custom metadata records and I got issue when my csv file contain values with comma. I also tried by wrapping values into double quotes but the issue isn’t resolved.

    If I was saved the file as CSV (UTF -8 ) then screen component gives error ‘DeveloperName. Please double check the API name of the field.Check console log for more info’.

    Please reply it asap.
    Thanks
    Prafull Jain

    Like

    • Looks like there is some issue with the encoding of CSV. Or there are some hidden characters.

      That’s why the DeveloperName is appearing(and being read) as ‘DeveloperName.

      Like

      • Hey
        This error ‘DeveloperName will not occur when i saved the file as CSV only. It only occurs when I was saved the file as CSV (UTF-8).

        My issue was that in CSV file, I have values that contain comma like Prafull, Jain. that will inserted as Jain.” in custom metadata records.

        Like

  9. Hi there,

    I am getting the below error – can you please help me?

    List index out of bounds: 6Check console log for more info.

    Thanks

    Like

  10. Ok, I feel like I’m missing something obvious here, but I’m new to unmanaged packages.
    I’ve installed the package to a sandbox org and I cannot find the flow anywhere. I’ve verified that the package is installed (v1.1), and found the other package components sprinkled around in there like the Dummy CMDT Type. But there’s no screen flow to be found. What am I missing?

    Like

    • I’m not sure if I packaged the flow too. 😄
      It should be easy enough to add the component to the screen flow and configure it.
      Feel free to reach out if you face any issues setting it up.

      Like

  11. As someone else wrote – I set the content document id + Metadata API name and run the flow but its empty. There is no job id generated and so sign it work. Also had a developer trying to make it work and still nothing.

    Like

  12. I have this problem as well and I can’t reply with a screenshot.

    Deploy Request Job ID: (not literally, just doesn’t show anything)
    Status: (again, doesn’t actually say it, just is empty)

    I’ve waited a long time and still no progress

    Like

  13. This tool is great and is functioning well. The only issue I’m experiencing right now is when I import some of my values they get extra quotations added to them. For example:
    *Imported value: 3/4″ Alum-mill V#2
    *Resulting CMDT record: “3/4″” Alum-mill V#2″

    I’ve ensured to format all as text, I’ve trimmed the cells, and do not have any blank cells in the last row. My tests show the presence of the wanted inch (“) symbol is what causes the issue, as if I remove that character then the issue goes away. However, I need those values. Do you know of any work arounds for this?

    Like

  14. Great tool! Have managed to insert new records, but struggling to update existing. Getting the error “problem”: “DummyCMDTType__mdt: could not find fields: Id”
    My CSV is like this, where Id is of the inserted record:
    Id,MasterLabel,TextField__c
    m0U5r000000L5ouEAC,New Test Label,Test 1

    Any ideas what I’m missing or doing wrong?

    Like

  15. This could be a huge time saver for me but I’m getting the following error.

    Custom Metadata Record Name: The Competency Item API Name can only contain underscores and alphanumeric characters. It must be unique, begin with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores

    My API Name is Competency_Item__mdt. Alos tried CompetencyItem__mdt

    Any ideas what might be wrong. I have the exact API name in the flow.

    Thanks.

    Like

      • Here’s the error. I am doing this in a sandbox. Screenshot doesn’t seem to be posting so…

        FSC_CSVToCMDTRecords Setup:

        Content Document ID: {!Single_Content_Doc_Id} which I used a first screen to upload the file and assign the content doc id to that variable.

        Customer Metadata API Name: Compentency_Item__mdt

        Error Message.

        “success”: false,
        “problemType”: “Error”,
        “problem”: “Custom Metadata Record Name: The Competency Item API Name can only contain underscores and alphanumeric characters. It must be unique, begin with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores.”,
        “lineNumber”: null,
        “id”: null,
        “fullName”: “CompetencyItem__mdt.1”,
        “fileName”: “customMetadata/CompetencyItem__mdt.1.md”,
        “deleted”: false,
        “createdDate”: “2023-01-08T21:07:20.075Z”,
        “created”: false,
        “componentType”: “CustomMetadata”,
        “columnNumber”: null,
        “changed”: false
        },
        {
        “success”: false,
        “problemType”: “Error”,
        “problem”: “Custom Metadata Record Name: The Competency Item API Name can only contain underscores and alphanumeric characters. It must be unique, begin with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores.”,
        “lineNumber”: null,
        “id”: null,
        “fullName”: “CompetencyItem__mdt.2”,
        “fileName”: “customMetadata/CompetencyItem__mdt.2.md”,
        “deleted”: false,
        “createdDate”: “2023-01-08T21:07:20.116Z”,
        “created”: false,
        “componentType”: “CustomMetadata”,
        “columnNumber”: null,
        “changed”: false
        },
        {

        Content Document ID: {!Single_Content_Doc_Id} which I used a first screen to upload the file and assign the content doc id to that variable.

        Customer Metadata API Name: Compentency_Item__mdt

        Like

      • Can you put the screenshot on g drive or something?

        Basically, I want to check if the CMDT api name matches what you’ve input in the flow config of the component.

        Like

  16. Figured it out. My mistake for sure but I’ll post so no one else does the same thing. I had the Label as sequential number like 1, 2, 3. When I filled out the Developer Name column, I forgot to add an X to the so it is X1, X2… Since API’s can’t start with numbers.

    Like

  17. Hello,

    When I’m running the component in the flow, the status keeps showing ‘deployment_in_progress’.
    In the console it shows the following:
    Subscribed to channel /event/MetadataDeploymentResult__e
    FSC_CSVToCMDTRecords.js:94 Unsubscribed from channel /event/MetadataDeploymentResult__e

    Do you have any idea why it’s failing?

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.