I'm looking to build a budgeting app where users can categories transactions (i.e. entertainment, rent, utilities, etc).
Is it possible to categorize plaid transactions by needs/wants? aka rent is under the need category, restaurants are under a want category.
I've looked here but am struggling to find any info: https://plaid.com/docs/api/products/#auth
You can use the /categories/get endpoint to see all the categories used by Plaid. From there, it should be pretty straightforward to essentially create a mapping where for each category you classify it as a need or a want. (This is a determination you'd have to make yourself; need/want info is not built into the API.)
Related
We have requirement to handle price dynamic (referring external system).
We would like to know, what is the best way to handle dynamic pricing among below :
Approach 1 :
Creating Price factory extension and overriding getBasePrice() method of customPricefactoryManager. Please confirm if it uses jalo layer.
Approach 2 :
In DefaultSLFindPriceStrategy we can customize getBasePrice() method.
If any other way too, please lets know.
We would like to know which approach can help to handle prices in addtocart operation, checkout and product page details pricing.
It is not good getting price in another system with integration online. ERP system used by few sales people but ecommerce site can be used by hundred customer in same time. ERP cannot be handle huge amount of connections. I prefer pushing price from ERP not pulling them from hybris side. On the other hand customer will be hate changing price while surfing between hybris pages. You need to plan correct time for updating price and re-calculating existing carts.
It is highly unlikely that you would need to override the above classes to get dynamic prices.
Hybris already provides OTB functionality to get prices for different-
Users
User groups
Currencies
Time range
If you are trying to get different prices based on above criterions then you can simply use the OTB price row model.Getting dynamic prices on different pages has many caveats-
The price on different pages i.e. Homepage, PDP, Cart, Checkout,
etc. might show different values confusing the customer.
It cannot
be indexed so the PLP page will almost always show a different price
value.
I want to use the many to one and other DB Relationship in micro-service architecture. In monolithic architecture we can create the entity relationship easily as they belongs to same project but in micro-service architecture how we can achieve the same.
Example:
There is one userDeatil service and other is productDetail service.Now there is third service called orderDetail and an order will have userID and ProductIDs associated with it. So how can we manage the relationship between 'user and order' and 'order and product'.
I have searched over net but didn't able to get the fair idea.There is another thread having same query but not having the clear answer. Link
In my opinion your case is about how you specify your services especially how you define the bounded context of each service !!
According to the situation above-mentioned I don't see any reason why the product service should know anythings about orders (even if it s just the order-id) and backwards. One more problem I see in this case: your services will not work if one service is not available (E.g when the product service it not online, your order service will not be able to work, because he needs the product details from the product service...).
I Think you should rethink the bounded contexts of your microservices. You should keep in mind:
ensure a loose coupling of the microservices
a microservice has always to work even other Microservices are not available (Resilience / Reliability).
The DDD (domain-driven-design) paradigm with its tools provides her a great help to assist you, during the definition process of your services, you encourage these qualities.
So, the following is JUST an idea (it s not a recommendation and you should review whether it matters for your business case) :
It seems like the "order" process is your core business domain. So you have to focus on it.
The user service (i hope you mean here the customer and not a user in terms of authentication/authorization) has only the responsibility to manage the customers, and may be their adresses, bank-Accountings etc.. It should not know anything about your orders or products.
The same is valid for the product service. It owns only data about products. It has no relation either to the customer nor to the order-service.
The order service by itself deals only with orders and should own only data that belong to an order (like ship Adress and some information about the product-items ordered). I think the customer-Id is also important here to keep the relation between the order and the customer. This way you can e.g get all orders made by a certain customer-id....
Building custom integration for a client with their e-commerce store and Zoho. They essentially have a referral program, for the easiest explanation. When someone purchases, we need to keep track of who the referring person was in Zoho and credit them - I have this all available. They only sell 1 product so we don't need actual financial / sales data, just the number of units attributed to the person in Zoho. They eventually want to be able to have reports generated in Zoho to tell them how many units each person is doing per month, who is their best performer, etc.
All the potential referral people are stored as Contacts in Zoho. My task is simply getting the data from the e-commerce site into Zoho, I do not have to create any reports or anything within Zoho. I have no experience with the Zoho world so I am not quite sure where the best place to even put this data as there are so many different Zoho "things" to use. I thought about using Invoices, but again we don't necessarily need the transaction data just counts and when they happened to produce the above stated reports.
I was finally able to reach someone at Zoho: Sales Orders are the right place to put this.
I am French, and I am developing a rental vacancies website. I would like add microdata on the rental vacancy offers (house, villa, appartment...), but I don't know which itemtype to use. Offer, Product, or an other?
http://schema.org/Offer
http://schema.org/Product
Thanks for your help.
There are several relevant schemas that apply, and you will be best off using a combination of them to represent your Offers. The Offer should be your root element, because it represents something that ican be purchased for a price. The itemOffered property has the Product type, so it is the logical extension point for embedding product content. Think of the Offer as your sales pitch and the Product as what you are actually selling. There is a metadata schema for Residences which include information about the domain of your Products. You could combine this with the Product itemscope or nest it within the Product (possibly via the model property).
Metadata from the GoodRelations schema can be used to extend schema.org's limited Product vocabulary as well.
I also see an opportunity for leveraging the Review schema (for any reviews in the corresponding Product property), and potentially TouristAttraction, if the rental's proximity to tourist attraction is a selling point. I also noticed that there is a LodgingBusiness schema that inherits from Organization. This should be used to encapsulate content about your actual client (or whoever rents out the apartments/villas to renters).
Use the new version of schema.org (0.99) with the following properties for the http://schema.org/Offer:
businessFunction; use http://purl.org/goodrelations/v1#LeaseOut as the value.
eligibleDuration: The duration for which the given offer is valid.
availabilityStarts: The beginning of the availability of the rental object.
availabilityEnds: The end of the availability of the rental object
If you need detailed patterns, please contact me via http://www.heppresearch.com/contact. We built the new e-commerce module for schema.org.
A key part of my current project is users having the ability to see what other users live near to them. What is the best way to implement this?
I would just ask for country, state and city but because this will be international I can't have a fixed drop down list of states/administrative regions for each country, so if users spell the name of their state differently this will hinder my ability to detect that users live in the same state.
Say for example we have an the Swiss canton "St. Gallen". Some user will spell that as "Saint Gallen", others as "St Gallen" and so on. Which is obviously problematic.
Could I just ask for the zip code and use that? I've found some zipcode tools online but I'm suspecting they don't work very well. Has anyone used them?
Thanks for your asnwers.
Shouldn't you base your query on geographical data rather than administration one? I mean instead of comparing cities/zip codes just find people within, let's say, 5 km from current user location. And if you let every user to choose his/her location on the map, this will be as simple as choosing it from a series of drop-down lists or entering a ZIP code. Also there is an emerging geolocation HTML feature.
Querying such an information is different story thou. You'll probably gonna have to use GIS capabilities of your database: MySQL, PostgreSQL, Oracle and others.