fa object external file template import error
can someone help me with following error, trying to use external file template first time and read some topics in community already i copied system defined file type and deleted few columns, nothing else is changed. in general i chose semi colon as separator my csv file looks like this thanks
hi,we have no formal “copy file type and template” from environment test to prod.this is what i’ve done hundreds of times.assuming you created a new file type or copied an existing template. - do this same process in prod (or the other environment), ideally keep the same name and description - just keeps things clean.then update the tabs so the file separator and date formant is the same. if you created any external file template controls update this as well,finally, - in the file template details, i delete all records in the new prod, and then use the copy / past object to copy the details from test to prod. rather than analyzing to see what’s different in the details between test and prod, if we know test works, i would typically delete the details and copy object from test to prod.if you had any formula in test you can manually copy these as well. it’s a few steps, but it only takes a couple minutes. best regards,thomas
sorry i took so long to respond on this post. i’ve had a busy week! so i found the issue. in my template for endpoints i realized i accidentally set them to provision using the external ip address of my pbx. changed it to internal and this fixed my issues :stuck\_out\_tongue: The object you are linking with was built with the option to use the static run-time libraries, whereas your DLL was (properly) built to use the DLL libraries. When you mix these you'll get complaints such as this.


Since Fortran objects don't care which library set is used (this is not true of C/C++), one option could be to set the Linker>Input property "Ignore all default libraries" (/NODEFAULTLIB) in your DLL project. You will then need to name the required libraries under Additional Dependencies. (You can use the dumpbin command on your DLL's object to see a list.)


If you can rebuild the external object, do so with the Fortran > Libraries > Disable default library search rules property set to Yes. Then you should be able to link it in without further issue.




[View solution in original post](/t5/Intel-Fortran-Compiler/Error-linking-to-external-obj-file/m-p/1144075#M138021) yeah this is me, that will break it even further.

you do not want the sshd template, no reason to be running sshd in your container.

look at your container config, (app.yml), delete the line with sshd it is legacy you do not need. we stopped using this pattern 3 or so years ago but forgot to remov… first, can you make sure there’s no chrome processes running in the background? you can check it via task manager. and try to import again. this is because you have a space between fields. 

program files (x86), avast software, it will continue to get this error because of the separation. try enclosing it into quotations. such as:get-content "c:\program files (x86)\avast software\business agent\log.txt"orget-content "c:\program files (x86)\avast software\business agent"\log.txt hi,

i can compile your code without error.

could you help to double check your makefile and environment?

environment is set by jetpack2.3.1

topic\_988388.cpp

#include "nvxio/application.hpp"

#include "nvx/nvx\_opencv\_interop.hpp"

#include <opencv2/imgproc/imgproc.hpp>

std::vector<cv::mat> tovisi… you’re on the right track.

is the name column of the choices table of the same column type as the 1st place and 2nd place columns?

please post a screenshot of the error message and the complete expression to which it refers. thanks for getting back to me [@michel1](/u/michel1)! in this case, i recommend you to contact our support team: [how to contact our support team ✉](https://forum.asana.com/t/how-to-contact-our-support-team/87774). unfortunately i don’t have the tools in the forum to check what’s causing the error in your screenshot but our support team should be able to assist here.

when you c… [image] andrei:

a quick fix is to comment the line in the "on message" tab for the function node that is troubled

when you add a module in "setup", the "import as" name is made available to the function tabs...

[image]

... so you dont need to declare it nor do you need to set/get it from co… the filename should be .env not environment.env.