Re: OTLT again

...

> One of these is seen as "better" than the other from several points of
view.
> If I start talking about OTLT, I'll start trashing, and I said I wouldn't
> do that.
>
> But the real discussion ought to be about user defined attributes. Is
this
> a good idea or a bad idea? If it's a good idea, then we can focus on the
> best way of implementing it. If it's a bad idea, we can focus on the
best
> way of talking the people who set the requirements out of asking for this
> feature.

Ok, the functionality is basically a registration of invoice data befor is sent to the ERP system. The registration is not done in the ERP anymore so it has to have the same functionality (hopefully better) and that means that we have to import all lookup data from the ERP. We have currently integration with almost 30 ERP systems and some have only a fixed amount of lookups (usually 8), some have x (again unually 8) "container" lookups, meaning that you can have unlimited lookups but can use only x on one document/invoice. And then there are those that have unlimited lookups and can use all of them at the same time. Now, we have to be able to import all the data in this last case too. So the requirements can't be changed in the sense that the functionality has to be there, but my implementation is still open. Received on Sat Nov 13 2004 - 16:20:36 CET