Trying to import using NP BO

JonP

Hi all,

When I import from a file, I don't want that file to persist anywhere in the system or the database. I just need it long-enough to import the data, then I want to throw it away. I figure the best way to do that is with a NP BO. And as a bonus, by keeping everything in memory, it should run faster.

So I created a NP BO that has a document attribute to hold the file, a plain text attribute to hold the record type and any selectable reference attributes as shown in this example:

The BO is part of a process that looks like this:

When I submit, immediately I get the "Import complete" message, but no import actually occurred.

My guess is that it doesn't like importing from a document attribute, but for some reason doesn't bother to throw an error.

ACDC

I recall using UNDEFINED/DEFINED on a document attribute does not work so well. A workaround is to use the file attributes function and monitor file size, besides why don't you keep it simple and do the import as normal and then delete the file afterwards in the same process

JonP

Can someone tell me what the normal way looks like? The documentation is a little vague. It pushes using the document attribute type to import as I am doing.

I changed the BO from NP to persisting and that didn't alter my previous experience.

Then I changed "Stored in" from "Database" to "File system" and added an attribute to set the path with the initial value of "C:\AwareIM\Files\". When I test it, I get the same quick success message, but nothing was imported and the imported file is stored as "Files" without an extension. Changing the path to include a filename with extension produces an error that the path is invalid.

idpSteve

Hi Jon,

I don't know about non persistence but from my experience I just store a document in the file system, then use IMPORT BO FROM ImportDoc.Path and that works for me.. Are you using the document path or the document attribute? If you're using the path then it should work fine..

To elaborate, I use the following:

ENTER NEW ImportDoc WITH ImportDoc.Path=SystemSettings.ImportCounter USING ImportForm

INCREASE SystemSettings.ImportCounter BY 1

IMPORT Boarder FROM ImportDoc.Path

Regards,

Steve

JonP

Thanks Steve, I had switched the attribute to storing in the file system, but I was still using the attribute instead of the path when importing in the FROM clause. Changing that didn't do the trick however.

Do your files store named as the last segment of the indicated path without an extension as mine do? Not having the csv extension might be the problem.

I'm curious about your Path attribute. You seem to be storing a number as the path because later you increase it by 1. Can you increase text by 1?

idpSteve

Hi Jon.

I have a number attribute in system settings that increments, and I just set the path(text) to the number(number). The files save as numbers without extensions, so I doubt that is your issue. You're welcome to send me your bsv, or just make a small import only bsv and I can check if I can see anything obvious.. Let me know.

Regards,

Steve

JonP

Thanks for the offer, Steve, but I'm starting to have some success now. I found the file ExportImport.txt on the forum (it wasn't in my installation as the user guide claimed), which helped give me a clearer understanding of the basics. I simplified my test by first removing the template, and then switching to a BO with fewer validations. That worked, so I just need to track down the validation that's causing the issue with the other test (and then maybe I can add back the template).

Cheers,
Jon