9 Replies Latest reply on May 17, 2013 5:24 AM by Halef

Custom Properties Import Can't Match on InterfaceID?

byrona May 10, 2013 1:06 PM

I want to use a spreadsheet to import a bunch of interface custom property data; however, it doesn't seem like I can match on InterfaceID? I had originally exported the list I am using from Orion with the InterfaceID as it's the only truly unique field that I have to work with. Since this is the only truly unique field I am curious why I can't match on this?

Re: Custom Properties Import Can't Match on InterfaceID?

byrona May 14, 2013 1:03 PM (in response to byrona)

Really would like a SW response on this if possible as this is something that I need to do.
Like Show 0 Likes(0)

Actions
- Re: Custom Properties Import Can't Match on InterfaceID?
  
  Michal.Pecenka May 15, 2013 4:36 AM (in response to byrona)
  
  Hi, what is your NPM version?
  
  Like Show 0 Likes(0)
  
  Actions
  - Re: Custom Properties Import Can't Match on InterfaceID?
    
    byrona May 15, 2013 9:28 AM (in response to Michal.Pecenka)
    
    I am running version 10.4.2
    
    Like Show 0 Likes(0)
    
    Actions
    - Re: Custom Properties Import Can't Match on InterfaceID?
      
      Halef May 15, 2013 10:23 AM (in response to byrona)
      
      Checking this on my 10.4.2, this is definitely a supported scenario. 10.4.1 didn't offer InterfaceId for export though - can you double check the CSV contains it? Also, the first page ('Select File") of Import is a bit tricky, you need to switch from "Nodes" to "Interfaces" in a dropdown.
      
      If all that looks right, please open a support ticket.
      
      Like Show 0 Likes(0)
      
      Actions
      - Re: Custom Properties Import Can't Match on InterfaceID?
        
        byrona May 15, 2013 10:31 AM (in response to Halef)
        
        I didn't do my export using that tool, InterfaceID is also not available as an export option. My export was done using a report I created in the report writer.
        
        Like Show 0 Likes(0)
        
        Actions
        
        Re: Custom Properties Import Can't Match on InterfaceID?
        
        Halef May 15, 2013 10:50 AM (in response to byrona)
        
        That's a path we didn't account for, but in general, any CSV should work. This is first few lines of the one that works for me:
        
        FullName,InterfaceID,CarrierName
        lab-whatsup - Software Loopback Interface 1 · Loopback Pseudo-Interface 1,1,
        lab-whatsup - WAN Miniport (SSTP) · Local Area Connection*,2,
        lab-whatsup - WAN Miniport (IKEv2) · Local Area Connection* 2,3,
        
        I believe this is case sensitive. Report writer might also use different encoding (not sure here, but I think the web import expects UTF-8. Best way to check is to do a test export from web and examine that file (I don't have tools for that handy right now).
        
        Do you just see different columns than InterfaceID in the wizard, or nothing at all?
        
        Like Show 0 Likes(0)
        
        Actions
        
        Re: Custom Properties Import Can't Match on InterfaceID?
        
        byrona May 15, 2013 10:52 AM (in response to Halef)
        
        In the import wizard I just don't see an option for InterfaceID.
        
        Like Show 0 Likes(0)
        
        Actions
        
        Re: Custom Properties Import Can't Match on InterfaceID?
        
        byrona May 15, 2013 12:18 PM (in response to Halef)
        
        Is exporting the data to an Excel Spreadsheet with Report Writer and then importing via the Custom Properties manager in the WebUI not an acceptable use case? According to the Custom Properties manager in the WebUI it accepts .xls files. I only used the Report Writer for my export as it allows me to be more specific about what I want to export.
        
        Like Show 0 Likes(0)
        
        Actions
        
        Re: Custom Properties Import Can't Match on InterfaceID?
        
        Halef May 17, 2013 5:24 AM (in response to byrona)
        
        It's definitely an acceptable use case. What I meant was, it's not the primary flow I'd expect.
        
        If the CSV looks fine (per what I wrote earlier), please open a support ticket and we'll look into this.
        
        Like Show 0 Likes(0)
        
        Actions

Go to original post