Docuref , change TypeId

(0) Share

Report

Posted on by Wvduren

1,435

Hello all,

At our company we have all product drawings attached to a product. The most recent drawings have a TypeId "Recent".

When something changes, a new drawing is attached. This new drawing again gets typeId "Recent". The problem is that a user then has to delete all the old drawings, and attach them again with TypeId "Old".
This because you cannot change the TypeId anymore once an attachment has been made.

Now I can update the TypeId manually quickly trough X++ (just select the docuref document, and update the typeId). This works fine in our test environment:

[quote]
while select forUpdate docuref where docuref.refrecid==5637164103

{
if(DocuRef.TypeId=="Recent")
{
docuref.typeId="Old";

ttsBegin;
docuref.update();
ttscommit;
}

[/quote]

My question is: is this safe? Can I just update it in the table? I would say yes, but I cannot understand why it is not possible to change it through the user interface if it would be that simple

Thanks in advance.

Kind regards, Willem.

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (1)

Community Member on at

Like (0)

Report

Hi Willem,

instead of updating at table level, why can't you write code to change the type id of previous records before inserting new record.

Find all the records in docuref table with docuref.ReftableId= tablenum(your table) and docuref.RefRecid = product.recid and set docuref.TypeId = "old" call this method before insert method.

Was this reply helpful? Yes No
Verified answer

Jesus R. ABASCAL 1,450 on at

Like (0)

Report

Users can't set to "OLD" typeId due to table field properties. TypeIs allows edit on create but not then.

I suggest you, create a button that runs a small action (Class) that update the typeId of select record.

Was this reply helpful? Yes No
Suggested answer

Jonathan Halland 11,310 on at

Like (0)

Report

Hi Willem.

This seems like a misuse of the TypeId field. The type of a document should not logically change once you have created it. i.e. The file has not changed, so its impossible for its "type" to have changed. Perhaps you should rather have an alternate field on your table called "Latest" where a user can select which one is the latest document.

Was this reply helpful? Yes No
Wvduren 1,435 on at

Like (0)

Report

Thank you all for your replies.

Raghuk35: what would be the advantage compared to the updating on table level?

Jesús: Yes that's what I will do. Thank you. I will update it on table level using a small class.

Jonathan: Yes I agree: It is a misuse with the goal to stay as close to the 'basic ax tables' as possible.

Thanks again!

Kind regards, Willem.

Was this reply helpful? Yes No
Jonathan Halland 11,310 on at

Like (0)

Report

Hi Willem.

I hope Jesus' solution will work for you. Just becareful that in your attempt to stay close to standard AX in table structure you are deviating in business logic which may have more serious repercussions than simply adding a new field. There is a reason they have disabled one from changing the type after creation.

An alternate could also be to have a display method on your table that simply displays "Recent" for the document with the latest createdDateTime field. That way you would not be changing the table or changing business logic.

Was this reply helpful? Yes No