Problems when creating XMLport

selece28

Hi all,
I have a problems, lets say i want to create an XMLport from Item table27
As we know, Item table27 have so many fields, so if i want to create an XMLport to generate all fields from that table, it took me a lot of time to type the tagname one by one. Is there an easy way to do this?

Thanks

ara3n

I'm afraid no, there isn't any easier way.

selece28

Ow, if thats the case, then there's nothing i can do about it, just have to start inserting all of the fields one by one myself

Thank you for your help ara3n

kine

Or you can export the XMLPort into text and use some good editor to generate the parts for each field. Or you can create some XMLPort generator within NAV to do that... :-)

ara3n

looking at the xmlport in text format. I don't see it as being userfriendly or easier. and one typo or syntax mistake will take you for ever to find it when you try to import it.

    { [{F82475A4-7677-401A-9F1E-D9A5E8E73077}];1 ;Unit_Price          ;Element ;Field   ;
                                                  DataType=Decimal;
                                                  SourceField=Item::Unit Price }

    { [{17DB260E-5832-46F2-AD96-E9BED66F2236}];1 ;Unit_Cost           ;Element ;Field   ;
                                                  DataType=Decimal;
                                                  SourceField=Item::Unit Cost }

kine

Yes, the new GUID must be generated, I forgot that one...

ara3n

Is there a reason why they are using GUID instead of integer as they are using in other objects?
They've started using them in menusuite and xmlports. and merging objects is almost impossible.

With menusuite you cana put them in different layer, but I'm guessing new objects types in 5.0 etc will have the same properties.

DenSter

Theoretically, using a GUID instead of integer will prevent us from ever having duplicate control numbers, which should ultimately make merging objects easier.