Good day to you all,

We have been using the File -> Import -> Batches -> Detail Only

We are having a problem with the period date which is being exported from the other application as 0.

We are now suddenly getting the error noted above and ponder if this an Adagio issue or a problem with the other vendor.

Is there some information I could get in relation to what the Adagio Ledger must have in this column or what it can accept?

Thanks in advance and,

Cheers, JK

I have now confirmed with the other vendor that their software has not been modified - ergo it was exporting 0 as the period and it was working...

Any ideas?

Thank you all and,

Cheers, JK

There is an option on the import template to set the period based on the date of the transaction. Check your import template.

Good day Andrew,

Thank you for the information.

I have checked all three tabs and did not find said flag.

I also moved the Period out of the template and as such it moved over to the defaulted fields and I was unable to do anything other than assign a period to it..

The option you describe is exactly what I am looking for though.

I am in Adagio Ledger..

Thank you and,

Cheers, JK

"now suddenly". What has changed in your setup recently? Ledger version?

John:
You're correct that the setting Andrew suggested isn't an option in the GL (it is in other modules). You could address this as a short-term solution by doing the following:

* On the Selected fields tab, insert "Filler" where the Period exists in the source file. Click on the "Filler" button and move it to the correct sequence
* On the "Default" tab, enter the correct Period number.

However this would not be my first suggestion. It has 2 problems: i) it only works if all transactions in the batch have the same Period and ii) you have to remember to change it every month.

I would go back to the 3rd party developer and ask under which conditions the Period would be output as a "0" (i.e. new fiscal year not set up yet?). It's not enough to say that the other appplication hasn't changed; neither has the Adagio GL!

Do you still have any of the past export files? Check the Period in those to prove that it wasn't 0 in past batches.

0 is a valid value for the 'Detail only' format for importing batches. If you access the Help file within Adagio Ledger and follow the link for 'Import File Requirements Notes' on the main help page, you will find this note within the section for importing batches in Detail Only format:

Fiscal Period can be 1 to 13 or “0” in the import file. If it is 0, the period will be determined based on the Fiscal Date.

When I attempt this with sample data and Adagio Ledger 9.0C, there are no errors. Thus Adagio Ledger is properly validating the 'Fiscal Date' field from the import file and assigning the fiscal period.

What you will need to determine from the import file created from the other application is what values exist for the Entry Number (if any) and the Fiscal Date. These would be the second and third columns (respectively) if you have an import template layout equal to the Default template (which I suspect you do). You cannot have details with different Fiscal Dates (belonging to different fiscal periods) within the same Entry.

You may need to investigate with your Adagio consultant what the file and template layouts are and how they are out of synch.

And the moral of the story (again) is that we should all read the "Help" notes more often!

>> Fiscal Period can be 1 to 13 or “0” in the import file. If it is 0, the period will be determined based on the Fiscal Date.

I went back to my notes and found this reference as well but also found that I was unable to make it work - a value always had to be there.

Upon further digging the other vendor confirmed that he did not change the software but did error on one of the translation forms used which led to the value of 0 in the exported file.

Once the other vendor fixed that problem we were once again able to import.

At the end of the day I'd like to thank everyone for the feedback and ponder why importing is not possible with a value of 0 in the fiscal period even though it is no longer an issue!

Cheers, JK

Was the date on the transaction that reported the error for a valid, open fiscal period?