That's exactly the case where Data::Diver is helpful!

This is my first exposure to Data::Diver, and I'm impressed and happy to put this in my bag of various scripts:

$ ./1.diver.pl $VAR1 = { 'product_id' => 'ABC123', 'unit_qty' => '1', 'price_excl_vat' => '1000' }; $ cat 1.diver.pl
#!/usr/bin/perl use 5.016; use warnings; use Data::Diver qw{ Dive }; use Data::Dumper; my $external_structure = { 'name' => 'Test product', 'id' => 'ABC123', 'data' => { 'enabled' => '1', 'internal_id' => '', 'urls' => { 'main_url' => '' }, 'price' => '1000', 'unit' => 'ST', 'unit_info' => { 'qty' => '1', 'gtin' => '1234567890' } } }; my %format = ( product_id => ['id'], price_excl_vat => [qw[ data price ]], unit_qty => [qw[ data unit_info qty ]] ); # (1) my $internal_structure = {}; for my $key ( keys %format ) { $internal_structure->{$key} = Dive( $external_structure, @{ $format{$key} } ); } print Dumper $internal_structure; __END__ $
Note that the second element of the path is unit_info, not just unit.

Well noted. This points out the problem of whether to "fix" the original post. If OP does, then both of our posts might need "fixing" too. My preference is to leave the warts on the original post.


In reply to Re^2: Mapping data structures through external source by Aldebaran
in thread Mapping data structures through external source by DreamT

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.