Data Virtualization

Hi,I’m relatively new to FME and currently doing some self-teaching for my company. At the moment, I’m trying to use an Excel Writer with a fanout expression to create hierarchical folders and files. The challenge is that I’m working with a bathymetric raster layer, and my workflow is primarily in CARIS, so the output files must be compatible with CARIS.I’ve tested several export options and found that .csv and .shp files work, but other formats do not. Does anyone have suggestions on alternative ways to create these folders and files while ensuring compatibility with .csar or caris compatible point cloud files?I also wonder if I am able to export contours as anything other than a shapefile/ can it be a .hob?My fanout expression is currently: @Value(ObjectName)Raw_Data\@Value(ObjectName)_BathymetricData.csv

I was following this article where i tried to create a WMS service. Everything works as expected in FME form. Using the OGC WMS (Web Map Service) reader i am able to trigger both workspaces and get the result as expected , in my fme server jobs i also see that 2 GetCapabilities.fmw workspaces are ran and 1 getPNG.fmw workspace. I tried importing the same WMS url into ArcGIS Online but i see that only the GetCapabilities.fmw workspace is ran and not the getPNG.fmw workspace. Does anyone have some idea over why the getPNG.fmw workspace is not triggerd by the ArcGIS Online client? Thanks in advance,Keller.

Hello everyone,I hope you are doing well.I encountered an issue when trying to polygonize text in DWG data that contains Japanese characters using the Transformer: TextStroker. The text was displayed as tofu (blank squares).When I tested the same process on FME Form 2025.1.1 (Windows 11), the text was polygonized correctly without any problem.If anyone has insight into possible misconfigurations or additional steps needed for proper handling on Linux, I would greatly appreciate your advice.Environment: OS: Linux Ubuntu FME Flow: 2025.1.1 Target language: Japanese Desired font: Noto Sans CJK JP Notes:Font recognition status on OS:>(base) ubuntu:/usr/share/fonts/opentype/$ fc-list>/usr/share/fonts/opentype/noto/NotoSansCJK-Regular.ttc: Noto Sans CJK JP:style=Regular>/us

My response coming back from the DV endpoint is different to the order of key value pairs in my JSON templater, why is this?  Is this expected? i.e we have no control?  

I’m having a problem with my API endpoint (both PUT and POST). It’s supposed to insert or update records in a PostgreSQL database. The database encoding is set to UTF-8, but unfortunately, any text data I send ends up stored with garbled characters (e.g. Polish letters are replaced by strange symbols).It doesn’t matter whether I call the endpoint from postman or directly from a browser the result is the same.Has anyone run into a similar issue? payload: {  "lok_miejscowosc": "Poznań"}Content-Type application/json; charset=UTF-8db result:lok_miejscowosc|---------------+PoznaÅ„        |

Hi I’m currently trying to acces the documentation of the API I'm making using data virtualization. The Swagger documentation page loads, but it seems to fail to get the correct server on which I have made the API. Due to this I can’t test any of the API calls. This is the link to the swagger documentation: https://fme-acc.nordend.eu/fmeserver/swagger-ui/?api=2fd53796-610d-4fb6-8a92-5c05335568e7#/default/getCollectionsThis is the error that chrome runs into when loading the web page.  Does somebody now what the issue could be? I have no reverse proxy on the server so I don’t think it is the same as what is described here: 

I would like to add the following folder, named "moi”, to my top level resource folders, and add it to the list in the picture below. I couldnt find that much information about it online, and i tried something, but it didnt work. I located the folder in the FME Flow program files, and added the folder, but that didnt work. It doesnt show up in the top level resources list, Does anyone know if it is possible to do this? And how?  Thanks in advance!  

I’m working through the Create a Manual Endpoint in Data Virtualization – FME Support Center however when it comes to the Make a Request from the Documentation section and clicking the ‘try it out’ button in the Swagger page, I get the following 401 response:Is this related to the time which the error lists as 15:48 GMT, however we’re on BST in the UK at the moment so it’s actually 16:48?  If so, how can I resolve it? Otherwise is it a simple authentication issue? - the tutorial says “the EnvionData API is authenticated by default” so I’m a little confused by this.

I’m experimenting with Data Virtualization, and has encountered a built-in error, it seems.Whenever I use a variable value with non-ascii characters (ÆØÅ in question), I get a nasty error:{ "message": "Error running Data Virtualization Workspace \"DV_LER 2.0_GET_schemas_table_data.fmw\" for API \"ler2\": An error has occurred. Check the logfile above for details"}The value in question is “Afløbsledning”, and the url swagger is using is:http://localhost:8080/api/ler2/schemas/myschema/table/afl%C3%B8bsledning/dataThe error in the Flow log file is:JSONTemplater_TABLE (XMLTemplaterFactory): The following error occurred near line 1, column 148 of the query:JSONTemplater_TABLE (XMLTemplaterFactory): "context item": undeclared variableJSONTemplater_TABLE (XMLTemplaterFactory): An error occurred while executing the 'ROW' queryJSONTemplater_TABLE (XMLTempla

Is there any plan to support receiving data in application/x-www-form-urlencoded with FME Data Data Virtualization endpoints? Currently, when creating an endpoint, the request body only allows application/json as the content type. In some cases, external applications or services can only send form-encoded data rather than JSON. Is support for form data planned in upcoming versions?

Is there a way to import the schema you’ve set up for an endpoint into your workspace? As I understand it, right now (build 25572) the schema that you define in Flow is only used to generate the documentation and you can copy and paste from there of course, but that still feels a bit unpolished.