best practice for extend field's length

(0) Share

Report

Posted on by Ganriver1

1,559

Hi Friends,

When we print 1099 for vendor, vendor address becomes a problem, in Tax1099IRSPayerRec table, MailingAddress field only holds 40 chars, which it will hold 'address1' and 'address2'.

Most vendors are fine, but, some are not. The field has ExtendedDataType of 'Tax1099Street', which is only 40 chars.

I don't know why Microsoft makes it only 40 chars, it is obvious not sufficient.

Anyway, what's best practice to enlarge the 'MailingAddress' field in 'Tax1099IRSPayerRec' table? Since this data type is used in many tables, if I extend data type, that seems to me it's over kill.

I have the same question (0)

All responses (5)

Answers (1)

Ganriver1 1,559 on at

Like (0)

Report

RE: best practice for extend field's length

Thanks a lot, Sergei.

Was this reply helpful? Yes No
Verified answer

Sergei Minozhenko 23,093 on at

Like (0)

Report

RE: best practice for extend field's length

Hi Ganriver,

In case if you just change Tax1099Street field length, the impact is minimal as it's used only in few places (according to cross-reference, couple fields on Tax1099IRSPayerRec table and display methods to fill these fields). And it's not a generic field, but quite a specific field for Tax1099.

Was this reply helpful? Yes No
Ganriver1 1,559 on at

Like (0)

Report

RE: best practice for extend field's length

Thanks for your response. I double checked the data type, it's used only in this Tax1099IRSPayerRec table, somehow when I sync it, it showed lots of tables and took quite some time.

I decided to modify the datatype, it seems it's easy route and can satisfy user. Since it's Microsoft generic field, what should I be careful for?

Was this reply helpful? Yes No
Suggested answer

Ramon_J 65 on at

Like (0)

Report

RE: best practice for extend field's length

If you guess that the customization impact of the EDT is huge I would try to go for another approach:

Maybe you could make an extension of the table an add a new 'replica' field but based in a customized EDT with the desired length, and then replicate or extended the 1099 report design and replace the standard field by the new one.

At least with this approach you isolate the impact to a table and a report and let the standard to keep using the original EDT as usually.

This has a drawback too: You will need to go back to check your custom report design if MSFT updates it in the future its behavior.

Another option would be to request MSFT to change the core EDT, but this is a long-term solution (if it has success).

Was this reply helpful? Yes No
Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

RE: best practice for extend field's length

Hi River,

Would it be an acceptable workaround to abbreviate/truncate the text in the 1099 report?

By doing this you might circumvent the issue.

Best regards,

Ludwig

Was this reply helpful? Yes No

Community site session details

best practice for extend field's length

Helpful resources

News and Announcements

Quick Links

Responsible AI policies

Andrés Arias – Community Spotlight

Congratulations to the August Top 10 Community Leaders!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates

Community site session details

best practice for extend field's length

Helpful resources

News and Announcements

Quick Links

Responsible AI policies

Andrés Arias – Community Spotlight

Congratulations to the August Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates