Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


ggt667 last won the day on June 6 2017

ggt667 had the most liked content!

Community Reputation

9 Neutral

About ggt667

  • Rank
    Street Stupid, Nerd Stupid, Geek Wiz

Profile Information

  • Title
    Philosopher, Partner, and Keyboard Masseur
  • Industry
    Logistics, horticulture production
  • Gender
  • Location
  • Interests
    Trikke T12 Roadster, bouldering, DIY woodwork

Contact Methods

  • Website URL
  • Skype
  • MSN
    iMessage: ggt667@me.com and FaceTime

FileMaker Experience

  • Skill Level
  • FM Application
    16 Advanced

Platform Environment

  • OS Platform
  • OS Version
    OS X, Arch linux, Joyent SmartOS, iOS

Recent Profile Visitors

7,684 profile views
  1. The initial issue is that I have to do 12 imports to FileMaker to import 1 real world XML document, and I have 7 real world XML document types I import multiple times pr day. Having FileMaker do the imports is backseat driving. What?!?
  2. One of the saddest parts about FileMaker is that we are not able to load XML from the command line, imagine being able to load like: /Applications/FileMaker\ Pro\ 18\ Advanced/FileMaker\ Pro\ 18\ Advanced.app/Contents/MacOS/\ FileMaker\ Pro\ 18\ Advanced layoutname bymatchingfieldnames << my.fmpxmlresult.xml from command line or even better With properly naming I would be able to load any document.
  3. Removing the need for double entry is a gain in itself.
  4. This depends on how you create the XSLTs. What is amazing about XSLT is when you dare to make more of them, and when you work with standards you can make XSLTs to split and join your other XSLTs. When I make XSLTs that are FileMaker centric, I make them in a way that I have a set of XSLTs that can build other XSLTs and specialized for each subset. Tip you can export complex XMLs from FileMaker, however you can only import them 1 table at the time; none relational. You can use the complex export as a template for how to split import data prior to import.
  5. How can I see the actual byte counter? Is there a /proc/ or similar that I can cat? As pr example: cat /proc/fmdataapi.allowance or similar. Is this done pr byte count of the raw HTTP query response? Or the body inside the HTTP response?
  6. "For inbound Data Requests (pulling data into the database on your FileMaker Server) you have unlimited API Data Transfer. For outbound Data Requests (pushing data out from the database on your FileMaker Server) you are limited to the API Data Transfer included with the Software along with any additional API Data Transfer that you purchase." sic - https://support.filemaker.com/s/article/Understanding-the-Data-API-Annual-Limits?language=en_US Does this mean that when I do a query `curl -kL -XPOST fmserver/fmi/data/v1/databases/some/params -d "more:params"` The query I send to FileMaker is for free? But its response does a countdown on my allowance?
  7. Here is the raw query( I'm not sure which parameters are required, far from all are filled in, and many appears to be double up ) that changing the Summary to XML does: This is a feature I miss in FileMaker being able to import XML using the HTTP verb _POST with a payload. It appears Brave claims to be FireFox, Safari and Chrome? The payload has been split by individual parameters below( Far from all are filled in ) ["term", "31618393+31618392%5Buid%5D+"] ["EntrezSystem2.PEntrez.PubMed.Pubmed_PageController.PreviousPageName", "results"] ["EntrezSystem2.PEntrez.PubMed.Pubmed_PageController.SpecialPageName", ""] ["EntrezSystem2.PEntrez.PubMed.Pubmed_Facets.FacetsUrlFrag", "filters%3D"] ["EntrezSystem2.PEntrez.PubMed.Pubmed_Facets.FacetSubmitted", "false"] ["EntrezSystem2.PEntrez.PubMed.Pubmed_Facets.BMFacets", ""] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.Pubmed_DisplayBar.sPresentation", "xml"] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.Pubmed_DisplayBar.sSort", "none"] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.Pubmed_DisplayBar.FFormat", "docsum"] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.Pubmed_DisplayBar.FSort", ""] ["email_format", "docsum"] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.Pubmed_DisplayBar.email_sort", ""] ["email_address", ""] ["email_subj", "31618393+31618392%5Buid%5D+-+PubMed"] ["email_add_text", ""] ["EmailCheck1", ""] ["EmailCheck2", ""] ["BibliographyUser", ""] ["BibliographyUserName", "my"] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.Pubmed_DisplayBar.FileFormat", "docsum"] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.Pubmed_DisplayBar.LastPresentation", "docsum"] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.Pubmed_DisplayBar.Presentation", "xml"] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.Pubmed_DisplayBar.PageSize", "20"] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.Pubmed_DisplayBar.LastPageSize", "20"] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.Pubmed_DisplayBar.Sort", ""] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.Pubmed_DisplayBar.LastSort", ""] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.Pubmed_DisplayBar.FileSort", ""] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.Pubmed_DisplayBar.Format", "text"] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.Pubmed_DisplayBar.LastFormat", ""] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.Pubmed_DisplayBar.PrevPageSize", "20"] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.Pubmed_DisplayBar.PrevPresentation", "docsum"] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.Pubmed_DisplayBar.PrevSort", ""] ["CollectionStartIndex", "1"] ["CitationManagerStartIndex", "1"] ["CitationManagerCustomRange", "false"] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.Pubmed_ResultsController.ResultCount", "2"] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.Pubmed_ResultsController.RunLastQuery", ""] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.EmailTab.EmailReport", ""] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.EmailTab.EmailFormat", ""] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.EmailTab.EmailCount", ""] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.EmailTab.EmailStart", ""] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.EmailTab.EmailSort", ""] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.EmailTab.Email", ""] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.EmailTab.EmailSubject", ""] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.EmailTab.EmailText", ""] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.EmailTab.EmailQueryKey", ""] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.EmailTab.EmailHID", "1r1WD96DIMUWZetUgmuwE3ML8uzkrFTHG4KcPHT1lo9Sj7pzeetkwhsdsqevcYZ8Uvlm1NtAw_TU8ieO9udbjsyLp8l7gDN9bj"] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.EmailTab.QueryDescription", ""] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.EmailTab.Key", ""] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.EmailTab.Answer", ""] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.EmailTab.Holding", ""] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.EmailTab.HoldingFft", ""] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.EmailTab.HoldingNdiSet", ""] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.EmailTab.OToolValue", ""] ["EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.EmailTab.SubjectList", ""] ["EntrezSystem2.PEntrez.DbConnector.Db", "pubmed"] ["EntrezSystem2.PEntrez.DbConnector.LastDb", "pubmed"] ["EntrezSystem2.PEntrez.DbConnector.Term", "31618393+31618392%5Buid%5D"] ["EntrezSystem2.PEntrez.DbConnector.LastTabCmd", ""] ["EntrezSystem2.PEntrez.DbConnector.LastQueryKey", "1"] ["EntrezSystem2.PEntrez.DbConnector.IdsFromResult", ""] ["EntrezSystem2.PEntrez.DbConnector.LastIdsFromResult", ""] ["EntrezSystem2.PEntrez.DbConnector.LinkName", ""] ["EntrezSystem2.PEntrez.DbConnector.LinkReadableName", ""] ["EntrezSystem2.PEntrez.DbConnector.LinkSrcDb", ""] ["EntrezSystem2.PEntrez.DbConnector.Cmd", "displaychanged"] ["EntrezSystem2.PEntrez.DbConnector.TabCmd", ""] ["EntrezSystem2.PEntrez.DbConnector.QueryKey", ""] ["p%24a", "EntrezSystem2.PEntrez.PubMed.Pubmed_ResultsPanel.Pubmed_DisplayBar.sPresentation"] ["p%24l", "EntrezSystem2"] ["p%24st", "pubmed"]
  8. While this is true from FileMaker's perspective I have several XSLTs that are first complete real world XML documents( MXML, MTML, OAG, UBL / EHF, and others, ) then split into parts for FileMaker specific imports.
  9. This may actually be a better example: https://www.devguru.com/content/technologies/xslt/elements-xslcall-template.html
  10. Thanks, this is most likely sufficient to have an opinion, however is there a public access point where these XMLs can be retrieved?
  11. The appropriate use of for-each is for the equivalent of FileMaker's value list.
  12. templates are like subroutines, you will have to define and call them. This was the first entry when I DDGed `xslt template call` https://www.w3schools.com/xml/ref_xsl_el_call-template.asp
  13. If CPU is of importance to you template will be spending way less CPU( and probably memory as well ) than for-each.
  14. Better write a template than a for-each
  15. According to tcpdump it connects to TCP 5003, however not UDP as pr nmap response.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.