How to overcome the Netsuite "you provided invalid field type: INLINEHTML"

Rajat Parashar — Sat, 05 Jun 2021 08:24:10 +0000

Many times, you want to add a field to your SuiteLet Sublist that is able accept dynamic values. For eg: a URL, Text or RichText.

I am pretty new to NetSuite but this is something I wanted to do for one of the client project. I could create two column fields. But the issue with this approach is that It creates two columns and as I told earlier I want value to be dynamic. It mean only one type of value will be present thus Allocating another empty column is useless here.

For this purpose, I came around FieldType.INLINEHTML & FieldType.RICHTEXT. But for both of these fields, I got an error saying that *you provided invalid field type: *. First of all, this is very strange why NetSuite is throwing this error at all if they have given these field types.

But I didn't find anything related on internet to resolve this error so I thought of a quirk.

I used a FieldType.TEXTAREA. Textarea supports rich text and we can embed HTML in them. This works perfectly. You can literally put anything there with styling.

If I missed something and You know how to fix the original issue, comments are most welcome.

Imperative vs Declarative, S.O.L.I.D and AOP(Aspect-oriented programming)

Rajat Parashar — Sat, 04 Jan 2020 19:32:22 +0000

My Introduction

I am a Software Engineer at one of the Retail based startups. This is my first job which I am following since June 2018. This series will be used as a scratchpad for my learning.

Let's dive in

AOP
Imparative vs Declarative
SOLID

AOP(Aspect Oriented Programming)

AOP is all about dividing parts of software into small modules. Adhering to AOP means separating various cross-cutting concerns of your software into small aspects that provide advice to your procedures(functions). In this way, we can apply extra functionality to our app without changing the codebase.

Crosscutting concerns can be:-

Background sync
Security
Logging
analytics
etc

All of the above tasks are not part of business logic(code which resembles the Idea of your app). These come under extra work. So If we have to change the code and invoke the above-mentioned tasks manually then it will resource consuming.

AOP gives us an idea of how can we shortcut these tasks.

AOP Terminology

Under AOP, various aspects advise your code. Aspects are the key unit of modularity.

Aspects - these are the classes or modules that apply some advice to your code. For eg - log every action in your app.
Weaving - weaving is the process of linking the advice to advised object.
Advice - It is a specific job which is done by aspects.

There are various types of advice-

After
Before
Around
AfterRunning
AfterThrowing

Yes, they work as they sound. Go over reference for more details.

Imperative vs Declarative Programming

As one-liner,Imperative Programming is all about telling the machine the path to follow for achieving something.In this case, machine itself does not know how to reach to a target, we tell it how.
Ex - Assembly language, C++

Conversely in Declarative Programming, we ask the machine what do we need machine does some internal magic and give us what we wanted. We have to explain the objective to machine.
Ex- HTML, SQL

a good explanation using SQL language

To illustrate even further, with imperative code you describe how to do what you want done. Conversely, declarative code enables you to describe what you want to do without worrying about how.

S.O.L.I.D Principles

Single responsibility Principle.
Open-closed Principle
Liskov Substitution Principle
Interface Segregation Principle
Dependency Inversion Principle

S.O.L.I.D stands for first five object-oriented design by Uncle Bob(Robert C. Martin).

Conclusion

AOP is an important concept that every Intermediate programmer should know. SOLID are very important concepts for becoming an expert coder.
Understanding the difference between Imperative and Declarative will make your life easier as a Frontend Developer.

DEV Community: Rajat Parashar