It seems unlikely to me that there's much demand for this field at all, never
mind demand for keeping both an ISIN and a national number, so I don't think we
need to separate it. The search function could use namespace as a disambiguator
for numbers, or users who encounter more than one flavor c
Hi Thomas,
Am 21.01.22 um 21:39 schrieb Thomas:
> And because of that, I am struggling to do a matching based on that
> field. As my bank, denotes the WKN (a unique identifier),
The WKN is only unique inside the german markets. If you also have a
french bank, they might send the SEDOL instead.
B
Thomas,
By far the simplest solution to your problem would be to use your favorite
scripting language to rewrite the CSV with the symbols you use for GnuCash.
As for the pricedb lookup by cusip and corresponding CSV column, sure, I think
that would be a fine addition for GnuCash v5.
Regards,
J
Thanks a lot for your hints John!
I think I'll need some time to find my way through the code and then try
to adapt based on the existing implementation.
Would you deem such a feature useful and worth implementing, so it might
- at some point in the future - find its way into the codebase? Or d
> On Jan 21, 2022, at 9:32 AM, Thomas wrote:
>
> Dear list,
>
> recently, I spotted a feature that I would love to have added to GnuCash. As
> I have a software development background, I could definitely contribute to
> the solution, but as it is quite some time ago that I developed in C++
Dear list,
recently, I spotted a feature that I would love to have added to
GnuCash. As I have a software development background, I could definitely
contribute to the solution, but as it is quite some time ago that I
developed in C++ and am new to contributing to GnuCash, I might need
some cu
