Currencies flow

flows
currencies
issue

#1

Hi team,

We are trying to extend Currency object with flow, tried it both via dashboard UI and API - flow for currencies slug created, custom field added, we see it on Currency object entry. But when we capture any value for this field - dashboard UI says “Successfully saved your currency” but right after when we open record there is no value saved before. Same for API - PUT to /v2/currencies/:ccy_id returns HTTP 200, but even in response payload there is no saved value for custom field.

See our API calls below:

1. create flow by call to /v2/flows
    {
      "data": {
    "type": "flow",
    "name": "currencies extension",
    "slug": "currencies",
    "description": "Extension to built-in currency to support ERC20 token specifics",
    "enabled": true
      }
    }
2. add custom field to flow by call to /v2/fields
    {
      "data": {
        "type": "field",
        "field_type": "string",
        "name": "tkncontract",
        "slug": "tkncontract",
        "description": "tkncontract",
        "unique": true,
        "enabled": true,
        "required": true,
        "relationships": {
          "flow": {
            "data": {
              "type": "flow",
              "id": "93b5fbfc-9894-4318-b61c-d94057dcdf99"
            }
          }
        }
      }
    }
3. try to set custom field value right on currency by call to /v2/currencies/:ccy_id
    {
      "data": {
        "type": "currency",
        "code": "SMP",
        "exchange_rate": 0.55,
        "format": "SMP {price}",
        "decimal_point": ".",
        "thousand_separator": " ",
        "decimal_places": 16,
        "default": false,
        "enabled": true,
        "tkncontract": "demo",
        "links": {
          "self": "https://api.moltin.com/currencies/236d0606-f8b8-4003-b30e-c1c2ec19a8f7"
        },
        "meta": {
          "timestamps": {
            "created_at": "2018-10-11T10:49:44.543Z",
            "updated_at": "2018-10-11T12:13:45.361Z"
          }
        }
      }
    }

Please, advise what we are doing wrong.


#2

Hi,

Thanks for letting us know and giving us some great steps to follow :slight_smile: I will attempt to replicate and feedback to you once I have more information.


#3

Hi @v.yarovoy

At the moment Currencies isn’t fully supported by the Flows functionality, however, it has been raised with our engineering team.

If possible, for our understanding would you be able to give us a use case around the way you wish to use Currencies?

Thanks

Drew


#4

Hi,

Thanks for getting back fast to us on this issue.

So, from 3 objects we planned to extend currently 1 is not covered by Moltin functionality - Currencies extension is not supported by Flows, right? Is it on product roadmap and if yes what’s preliminary planned release date for this functionality to go live?


#5

Just confirmed with team - this is critical gap for us, because we have no other place on Currency object to use for custom data we need.
We checked there is even no Description attribute on currency means we have no chance to store required data


#6

hi @v.yarovoy

You could, in theory, create a flow separate to the currency object to store data in with a field in the new object with a unique identifier for the currency.

For example:

flow name: contracts
flow fields:
initial amount : int/string
token contract address : string
currency : currencyID

It would take a few extra calls as filtering wouldn’t be available but you could do a ‘GET’ all entries from ‘contracts’ and then find the data via your application.


#7

Ok, I see your point - we talked on similar workarounds during past hour.

But what’s your concern regarding objects extension - once done for several entities (order, product etc) what prevents from applying same approach to other entities?


#8

Hi,

We decided to try Flow + Entry record for this flow.

In your opinion - is there any tricky aspects / limitations of Flow+Entry combo which may appear for example after certain platform usage period?


#9

At the moment you can’t get an Entry by the field slug, and the scenario I outlined above but we are continually working on and improving Flows and the API, in general, to ensure I customers get the best possible commerce experience.

Thanks,

Drew